Quick Notes118 words
Code coverage analysis — quick notes
Code coverage — quick notes
| Item | Detail |
|---|---|
| Publish task | PublishCodeCoverageResults@2 |
| Coverage-format examples | Cobertura, JaCoCo; v2 accepts several other formats |
| Test result formats (different!) | JUnit · NUnit · VSTest · xUnit · CTest |
| Coverage measures | Which lines executed |
| Coverage does not establish | Good functional verification by itself |
| Azure Repos PR gate | Set a diff target, then require the pipeline's codecoverage status as branch policy |
The status is advisory until the branch policy makes it required. Coverage collection happens before publication.
Primary sources
- https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-400
- https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v2
- https://learn.microsoft.com/en-us/azure/devops/pipelines/test/review-code-coverage-results
- https://learn.microsoft.com/en-us/azure/devops/repos/git/available-pr-status-checks
- https://learn.microsoft.com/en-us/visualstudio/test/using-code-coverage-to-determine-how-much-code-is-being-tested
- https://learn.microsoft.com/en-us/power-bi/developer/visuals/unit-tests-introduction
- https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/publish-test-results-v2