Quick Notes139 words
Implementing tests in a pipeline — quick notes
Tests in a pipeline — quick notes
| Item | Detail |
|---|---|
| Separate publish task | PublishTestResults@2 when the selected runner/task leaves supported files and does not publish them |
| Supported formats | JUnit · NUnit · VSTest · xUnit · CTest |
| After an earlier failure | succeededOrFailed() in a non-cancelled run; always() also covers cancellation |
mergeTestResults | true combines files; more than 100 files are merged even when false |
| Parallelism | Multiple agents + capacity + strategy: parallel + independent slices |
Integrated test tasks can publish automatically. Publication feeds Tests and Test Analytics; job/task failure plus build validation supplies the merge gate. A standalone publisher's failTaskOnFailedTests default is false.
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-test-results-v2
- https://learn.microsoft.com/en-us/azure/devops/pipelines/process/conditions
- https://learn.microsoft.com/en-us/azure/devops/pipelines/test/review-continuous-test-results-after-build
- https://learn.microsoft.com/en-us/azure/devops/pipelines/test/parallel-testing-any-test-runner
- https://learn.microsoft.com/en-us/azure/devops/pipelines/test/test-analytics
- https://learn.microsoft.com/en-us/azure/devops/pipelines/test/review-code-coverage-results
- https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies