meteor-coverage icon indicating copy to clipboard operation
meteor-coverage copied to clipboard

Server and client coverage for Meteor

Results 12 meteor-coverage issues
Sort by recently updated
recently updated
newest added

"No coverage information has been collected" despite server tests passing as well as client tests passing when opening the browser, when going on localhost:3000/coverage. i followed the guide thoroughly, adding...

bug
help wanted

I followed the README instructions to run my coverage but all `.tests.js` files are included. Even explicit exclude pattern in `.coverage` do not work: ```js "exclude": [ "**/tests/*", "/**/*tests*" ]...

Expected behavior: That tests run consistently whether in coverage mode or not. Specifically that stack traces would contain the same paths. These paths are used by testing tools like `snap-shot-it`...

I am using enzyme for testing. Mount/Shallow test cases are passing but coverage is not increasing. ## Expected Behavior When a test case passes, the coverage should increase. ## Current...

## Expected Behavior On opening localhost:3000/coverage, it should show coverage ## Current Behavior On localhost:3000/coverage, it says no coverage has been reported but all tests have run successfully. Also for...

Is there a demo of the result? A nice html page?

I am running meteortesting-mocha package to run coverage and it is working fine on OSX but not on Windows 10. Under coverage folder, few files are created e.g, index.html: `...

## Expected Behavior The report `out_text_summary` should output something. ## Current Behavior The report `out_text_summary` does not output any report file and always outputs the message `coverage error: Failed to...

Any intentions to make this Meteor 3.0 compatible? Most of the work should be only about dependencies. Would you review a PR if I provide one?

This will make the package fully 3.0 aware ## TODOS - [x] npm deps updated - [x] test app 3.0 updated - [x] local lint passing - [x] local tests...