You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Angular 6 Unit Test Coverage - reporting not accurate #26020
[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:
Current behavior
Unit test coverage reporting is no longer accurate (shows missed branches outside of logic e.g. in imports)
Expected behavior
Unit test coverage accurately reports coverage.
Minimal reproduction of the problem with instructions
Create a new angular 6 project: ng new angular6-coverage-issue
Execute tests with code coverage ng test --code-coverage
View HTML report
What is the motivation / use case for changing the behavior?
The motivation is to fix coverage reports so they can be used as an accurate measure.
Activity
jhage-accesso commentedon Sep 19, 2018
Duplicate of angular/angular-cli#11672
benlesh commentedon Sep 19, 2018
This was closed by: angular/angular-cli#12291
thorstenherbst commentedon Jul 15, 2019
Hi @ALL,
i have the same problem. Itryed already source-maps:true and the problem stays the same. Reporting is not accurate.
Heres my configuration:
##angular-cli
package.json
ts-config
angular.json
Help is very appreciated.
Thanks in advance.
angular-automatic-lock-bot commentedon Sep 15, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.