-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Code Coverage File Paths #382
Comments
We should be consistent:
|
The fix breaks minimatch functionality when negation is used in a pattern due to the fact that path.resolve returns the absolute path with the negation no longer at the beginning of the pattern. |
Thanks @ngiebel that's a bug, I created an issue for it... |
Merged from master to stable. Closes #382 Conflicts: lib/config.js test/unit/config.spec.coffee
In the documentation for Code Coverage (http://testacular.github.com/0.6.0/config/coverage.html) there is no specific direction about the file paths that the code coverage preprocessors use. The assumption could be that they use the basePath value, but after looking at the examples in Testacular and Istanbul it appears that the path for each file must be preceded by "**/".
Some clarity in the documentation would be helpful.
The text was updated successfully, but these errors were encountered: