Code coverage shows line- 0 of n covered
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, csharp
- Domain
- ci-cd, testing-qa
Research direction
Start with Logs.zip and the VSTest@2 pipeline configuration, then review how Microsoft.CodeCoverage 17.14.1 is used with C# .NET Framework 4.8.1 DLL test assemblies. Check the issue's questions about Microsoft.NET.Test.Sdk, referenced PDB files, and test-assembly setup; done means identifying the configuration requirement that explains the zero covered lines.
Written by the indexing model from the issue text.
Description
I'm using Microsoft.CodeCoverage 17.14.1 and running the tests on Azure DevOps pipeline using the VSTest@2 task.
The CodeCoverage report is getting generated, and assemblies with the respective PDB's are present in the same directory.
The Target platform of test projects is .NET Framework v481, and tests are written in C# and have DLLs as test assemblies.
I've not added the reference of the Microsoft.NET.Test.Sdk to the test projects and haven't added the props and targets of the same.
The report says 0 lines covered out of n number of coverable lines.
Is it required to add the Microsoft.NET.Test.Sdk reference to my test projects to get the code coverage stuff working?
Is Microsoft.CodeCoverage 17.14.1 capable of covering the C# test assemblies' code coverage?
Does it need to have all PDB files on which test assemblies have references?, I mean the projects on which tests are being performed using test projects?
- Dominant language
- C#
- Stars
- 125
- Forks
- 17
- Avg merge
- 1h 17m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/codecoverage
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/codecoverage#246 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
microsoft/codecoverage#237 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/codecoverage#234 · 1 comment · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/codecoverage#233 · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
microsoft/codecoverage#232 · 6 comments ·
All issues in microsoft/codecoverage
Similar issues
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·
-
.NET Flaky Test Testing Tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-dotnet#5617 · 1 comment ·
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·