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

Investigate coverage support for yerbamate child execution #5

Closed
angrykoala opened this issue Oct 22, 2016 · 4 comments
Closed

Investigate coverage support for yerbamate child execution #5

angrykoala opened this issue Oct 22, 2016 · 4 comments

Comments

@angrykoala
Copy link
Owner

The scripts executed with yerbamate are not covered by a coverage tool like istanbul (as they are processed from a child_process). Investigate if is possible to get coverage information of those files.

@angrykoala angrykoala modified the milestone: 1.0.0 Oct 22, 2016
@angrykoala
Copy link
Owner Author

This could be useful: https://github.com/istanbuljs/nyc

@angrykoala
Copy link
Owner Author

Also gotwarlost/istanbul#97

@angrykoala
Copy link
Owner Author

The tool nyc supports spawn coverage.

Executing tests using yerbamate with nyc as coverage tool should cover files properly:

Usage Example:

"scripts":{
 "test": "nyc --reporter=lcov mocha"
}

Disclaimer: using nyc heavily affects on performances when testing using yerbamate (around 2~4 times more for each test). Use only when coverage is required.

Update readme with this data.

Using nyc is up to the user, investigate options to integrate this feature with yerbamate

@angrykoala
Copy link
Owner Author

nyc is very slow when processing tests with children, if integrated with yerbamate, use as an option

@angrykoala angrykoala added this to the 1.2 milestone Dec 30, 2016
@angrykoala angrykoala modified the milestones: 1.2, 2.0 Jul 7, 2017
@angrykoala angrykoala removed this from the 2.0 milestone Jul 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant