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

Question: Active logging or suggestions how to investigate a strange functionality #1653

Open
Tbd19 opened this issue Apr 27, 2024 · 1 comment
Labels
question This issue is a question

Comments

@Tbd19
Copy link

Tbd19 commented Apr 27, 2024

I have a Web Api with multiple endpoints that are being tested with Integration tests.
Now we want to generate report for code coverage but for some reason they are 0% coverage.
And I got to this point:
When I filter for a single endpoint the code coverage is NOT 0% and it works as expected
When I filter for 2 or more endpoints the code coverage becomes 0%.
The command is similar just the filtering is different

How can I determine what makes the code coverage be 0% when doing filter for each it is not 0%

PS: None of the tests are failing.

@github-actions github-actions bot added the untriaged To be investigated label Apr 27, 2024
@Bertk
Copy link
Collaborator

Bertk commented Jul 26, 2024

Hi, you can use the diagnostic logging. You find the relevant information here: https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/Troubleshooting.md#collectors-integration

e.g --Diag:"log.txt;tracelevel=verbose"

@Bertk Bertk added question This issue is a question and removed untriaged To be investigated labels Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This issue is a question
Projects
None yet
Development

No branches or pull requests

2 participants