Skip to content

Inaccurate Coverage/Highlighting in Code Coverage for Libraries in Projects #11832

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

Closed
frankrue opened this issue Aug 9, 2018 · 3 comments
Closed

Comments

@frankrue
Copy link

frankrue commented Aug 9, 2018

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [x] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

Node v9.5.0
NPM v5.6.0
ng v6.1.0
macOS High Sierra

Repro steps

  1. Create a basic Angular project
  2. Enter the project folder
  3. Generate a library
  4. Test that library & create code coverage
  5. Open the coverage HTML
  6. Navigate to src/lib/ and then any file (in my screen shot, I chose test-lib.component.ts)
ng new test-lib-app
cd test-lib-app
ng generate library test-lib
ng test test-lib --watch=false --code-coverage
open coverage/index.html

The log given by the failure

coverage-oddity

Desired functionality

Code coverage should be 100% and the highlights should not include portions of the strings in the import call, icons around the code, etc.

Mention any other details that might be useful

No other details.

@frankrue frankrue changed the title Inaccurate Coverage/Highlighting in Code Coverage for Projects Inaccurate Coverage/Highlighting in Code Coverage for Libraries in Projects Aug 9, 2018
@frankrue
Copy link
Author

frankrue commented Aug 9, 2018

This seems to be the same issues cited here: #11672.

@frankrue
Copy link
Author

frankrue commented Aug 9, 2018

Whatever the problem is, Issue #11672 will likely deal with it, so I'll close this Issue.

@frankrue frankrue closed this as completed Aug 9, 2018
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant