Skip to content
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

Karma-coverage not generating coverage reports for large projects. #21015

Closed
cklogs opened this issue May 31, 2021 · 2 comments
Closed

Karma-coverage not generating coverage reports for large projects. #21015

cklogs opened this issue May 31, 2021 · 2 comments

Comments

@cklogs
Copy link

cklogs commented May 31, 2021

Hi there,

I am posting an issue here in the core repo because I have not received feedback from any maintainers on karma-coverage since posting this issue earlier this year.

Because of this deprecation warning, teams such as ours with relatively large test suites are nervous that we'll eventually lose coverage reports once karma-coverage-instanbul-reporter is no longer supported.
image

Please advise on how to proceed and if this issue can be elevated to the core team's triaging.

@alan-agius4 alan-agius4 transferred this issue from angular/angular Jun 1, 2021
@alan-agius4 alan-agius4 added needs: discussion On the agenda for team meeting to determine next steps area: devkit/build-angular labels Jun 1, 2021
@ngbot ngbot bot added this to the needsTriage milestone Jun 1, 2021
@dgp1130
Copy link
Collaborator

dgp1130 commented Jun 17, 2021

Hey @cklogs, this is a tough situation to be stuck in. Unfortunately this seems like mostly a karma-coverage issue, so we hope they are able to give some direction on how to fix your particular problem which would be the ideal solution here.

We are planning to support just karma-coverage in the CLI and want to stick with official solutions as best we can. We don't want to continue supporting two test coverage solutions long term and our hope is that karma-coverage will be able to provide the necessary user support.

In the mean time, there's nothing actionable on this from the Angular side, so I'm closing this issue.

@dgp1130 dgp1130 closed this as completed Jun 17, 2021
@dgp1130 dgp1130 removed the needs: discussion On the agenda for team meeting to determine next steps label Jun 17, 2021
@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 Jul 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants