DP-750 · 4.3.3 · Deploy and maintain data pipelines and workloads
Testing strategy
Implement a testing strategy, including unit tests, integration tests, end-to-end tests, and user acceptance testing (UAT)
Layer unit, integration, end-to-end, and user acceptance tests so defects are caught at the cheapest appropriate stage.
Place tests in the delivery path
Tests are strongest when they gate the path from local development through version control and CI/CD into higher environments. The diagrams below separate unit, integration, and pipeline-level checks.
Build a test pyramid
- User acceptance testingBusiness fit
- End-to-endComplete deployed workflow
- IntegrationComponent boundaries
- Unit testsIsolated deterministic logic
Use many fast, narrow tests and fewer broad, expensive tests so defects are caught at the cheapest useful layer.
Match test to question
- One transformation must be correct in isolationUnit test
- Real components must work togetherIntegration test
- Full deployed path must succeedEnd-to-end test
- Users must accept the business outcomeUAT
Passing technical tests does not prove that the workflow meets user needs.
Run tests before promotion
Automated tests belong in pull-request and deployment gates, not only after code reaches production.
Key points
- Unit: Tests isolated transformation logic quickly
- Integration: Tests components with real interfaces or representative services
- End-to-end: Runs the deployed workflow through critical paths
- UAT: Confirms the solution satisfies user and business expectations
Exam trap
Do not rely only on end-to-end tests; slow feedback makes simple logic defects expensive to diagnose.
Sources · 2 Microsoft Learn pages Show ▾
Checked on October 4, 2026. Report a problem
Go deeper on Microsoft Learn
Checked against Microsoft Learn on October 4, 2026. Report a problem with this card