Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add code coverage stats #2

Merged
merged 1 commit into from
Jul 8, 2016
Merged

Conversation

dougluce
Copy link
Contributor

@dougluce dougluce commented Jul 8, 2016

Electron-mocha makes things like this a little difficult. Luckily, @inukshuk in jprichardson/electron-mocha#19 (comment) figures out a way to get around it. It's a bit of effort but does work in the end.

An npm module might come out with these clues embedded in it and the coverage.js can be removed.

Electron-mocha makes things like this a little difficult.  Luckily,
@inukshuk in
jprichardson/electron-mocha#19 (comment)
figures out a way to get around it. It's a bit of effort but does work
in the end.

With any luck an npm module will come out with these clues embedded in
it and the coverage.js can be removed.
@Johnny11 Johnny11 merged commit b42092e into rantomizer:master Jul 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants