Quick Notes171 words
Comprehensive testing strategy — quick notes
Testing strategy — quick notes
| Context or type | Scope | Placement |
|---|---|---|
| Local development / inner loop | Selected fast, relevant checks | Before push and throughout development |
| Unit test | One isolated component | Frequently, including PR validation |
| Integration test | Components plus supporting infrastructure | When required dependencies are available |
| Load / performance test | Expected and peak traffic | Start early; repeat in staging or a production-like environment |
- Shift left: detect defects as early as practical; defects found late can cost more or become impossible to correct.
- Local is a feedback context, not a test taxonomy level.
- Give load tests measurable thresholds and place them according to cost, risk, and environment readiness.
Trap: use reruns to detect or mark flakiness, not as resolution. Track and analyze the test, then fix or remove it.
Primary sources
- https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-400
- https://learn.microsoft.com/en-us/training/modules/implement-pipeline-strategy/5-design-implement-comprehensive-test-strategy
- https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-best-practices
- https://learn.microsoft.com/en-us/aspnet/core/test/integration-tests
- https://learn.microsoft.com/en-us/azure/well-architected/performance-efficiency/performance-test
- https://learn.microsoft.com/en-us/devops/develop/shift-left-make-testing-fast-reliable
- https://learn.microsoft.com/en-us/azure/well-architected/operational-excellence/workload-supply-chain
- https://learn.microsoft.com/en-us/azure/well-architected/operational-excellence/testing
- https://learn.microsoft.com/en-us/azure/devops/pipelines/test/flaky-test-management