-
Notifications
You must be signed in to change notification settings - Fork 12k
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
feat(test): extend karma.conf.js w/ kjhtml reporter #4567
Conversation
See related [PR 4567](angular/angular-cli#4567) in `angular-cli`
See related [PR 4567](angular/angular-cli#4567) in `angular-cli`
I think it would be a better reporter than just having a blank screen. |
@@ -31,8 +35,8 @@ module.exports = function (config) { | |||
environment: 'dev' | |||
}, | |||
reporters: config.angularCli && config.angularCli.codeCoverage | |||
? ['progress', 'karma-remap-istanbul'] | |||
: ['progress'], | |||
? ['progress', 'karma-remap-istanbul'] //, 'kjhtml'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM aside from the leftoever comment.
LGTM |
f6da259
to
7d78f4a
Compare
0ba7345
to
2709911
Compare
karma-jasmine-html-reporter (kjhtml) displays Jasmine test runner in the test browser.
2709911
to
429b0d2
Compare
will it be possible to view the report at a later point in time ? (like the coverage reports) As part our CI, we have to run our unit tests using 'Phantom JS' & we would like to review the results later |
karma-jasmine-html-reporter (kjhtml) displays Jasmine test runner in the test browser. Close angular#4567
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Add karma-jasmine-html-reporter (kjhtml) which displays Jasmine test runner in the test browser.
We use this in docs testing chapter so users can visualize their tests in the test browser rather than see a blank page. Convenient for exploring broken tests and re-running certain specific tests.
Has no apparent ill-effects on CI. We run these tests with this config in docs CI.
Deliberately excluded from the test/code-coverage combo ... for no great reason other than I thought someone who was running with code-coverage wouldn't want it.