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

Support for 'perTest' coverage analysis for Mocha (client side) #11

Closed
simondel opened this issue Feb 16, 2016 · 5 comments
Closed

Support for 'perTest' coverage analysis for Mocha (client side) #11

simondel opened this issue Feb 16, 2016 · 5 comments
Labels
🚀 Feature request New feature request

Comments

@simondel
Copy link
Member

Browser based Mocha tests are not yet supported. This feature could use the Karma test runner. See #10 for server sided Mocha support

@simondel
Copy link
Member Author

Existing projects such as grunt-mocha, which uses PhantomJS, can be used as reference.
The Mocha API can also be viewed in the Mocha source

@nicojs
Copy link
Member

nicojs commented Jul 19, 2016

I'm not sure about this issue. I think mocha is already supported as long as you use a test runner that supports the mocha framework. For example, you can use karma right now (of course at this moment without a mochaTestSelector). Unfortunately, grunt-mocha is not a clean test runner, as it adds grunt into the mix. @simondel How would you go about supporting these kind of test runners?

@nicojs nicojs changed the title Mocha support (browser) Support for 'perTest' coverage analysis for Mocha (client side) Nov 28, 2016
simondel pushed a commit that referenced this issue Apr 21, 2017
* feat(stop-karma): Stop karma on dispose

Stop karma on dispose using the new `karma.stopper.stop` api. Only resolve the promise if it stopped.

* test(chai-setup): Add chai setup
simondel pushed a commit that referenced this issue Apr 21, 2017
* feat(stop-karma): Stop karma on dispose

Stop karma on dispose using the new `karma.stopper.stop` api. Only resolve the promise if it stopped.

* test(chai-setup): Add chai setup
@simondel
Copy link
Member Author

simondel commented Jan 8, 2018

We haven't done anything for this in two years so let's close it.

@simondel simondel closed this as completed Jan 8, 2018
@nicojs
Copy link
Member

nicojs commented Jan 8, 2018

I've done some work on this issue recently during the revamp of the mocha test framework. It might actually already work. I should be able to test it this week. Let's keep it open for now.

@nicojs nicojs reopened this Jan 8, 2018
@simondel
Copy link
Member Author

simondel commented Jan 8, 2018

Great! I'll add a proper tag.

@simondel simondel added the 🚀 Feature request New feature request label Jan 8, 2018
sanderkoenders pushed a commit that referenced this issue Jul 6, 2018
The testRegex attribute of the configuration passed to Jest may be left undefined, causing Jest to fall back to its default
(/__tests__/.*|(\\.|/)(test|spec))\\.jsx?$

That will result by default in a wider selection of test files being selected.
This may help with #11
nicojs pushed a commit that referenced this issue Jul 8, 2018
The testRegex attribute of the configuration passed to Jest may be left undefined, causing Jest to fall back to its default
(/__tests__/.*|(\\.|/)(test|spec))\\.jsx?$

That will result by default in a wider selection of test files being selected.
This may help with #11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 Feature request New feature request
Projects
None yet
Development

No branches or pull requests

2 participants