-
Notifications
You must be signed in to change notification settings - Fork 249
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
Console only output still makes files. #24
Comments
Ya, true story. Tried |
👍 When running with Grunt, the following caused a coverageReporter: { reporters: [
{
type: 'html',
dir: 'dist/coverage/'
},
{
type: 'text-summary'
}
] }, Which is a bit odd as it leaves the tree with:
|
Now that there's a PR that fixes this, can we expect a fix? |
Are there any updates on this issue? |
Yep, same here.
Coverage creates two folders, on under root directory (always empty) and the second one inside |
* [email protected]: Includes fix for karma-runner/karma-coverage#24. We can remove the workaround config in text-console that was there to prevent an unwanted directory from being created. * [email protected]: Includes support for "chromium-browser" (in addition to "chromium") so we can eventually remove the hack in Jenkins that exports CHROME_BIN=chromium-browser. Change-Id: Ie360a93b2324d4a0736bbd86939e4c965574ae0b
* Add grunt-cli so that users don't need grunt-cli pre-installed globally. * [email protected] Fixes karma-runner/karma-coverage#24 * [email protected] Fixes karma-runner/karma-chrome-launcher#41. This will allow our Jenkins setup to rid the CHROME_BIN hack, after all projects have updated. * [email protected]: Addresses T90816. Change-Id: I49eb93e590e475536bbaaa30b83ea888390190d2
Even with no
dir
oncoverageReporter
, there are still files / directories made.The text was updated successfully, but these errors were encountered: