Running Azure Integration Tests in CI/CD
A development team wants automated integration tests to run whenever code changes.
Advanced · DevOps engineer · Integration design
Scenario overview; the standalone tutorial and its executable artifacts are not yet published. The proposed workflow still needs end-to-end implementation and verification.
What Quinzee contributes
An isolated environment per job avoids depending on a shared cloud development subscription.
The proposed example
Design a GitHub Actions job that prepares the pinned environment, deploys fixtures, runs compatibility checks and retains failure evidence.
Required capabilities
A disposable source-built environment and the locked compatibility clients.
Boundaries and remaining work
A local pass covers the exercised contract; validate permissions, scale and failure behavior on Azure separately.
What to verify
- Verify runner architecture, Docker access and dependency caching.
- Collect test results before controlled shutdown; keep credentials out of uploaded logs.
Read the three perspectives
- The Book of Quinzee: Deliver work with Service Bus
- The Book of Quinzee: Service compatibility and limits
- Quinzee Administrator’s Guide: Diagnose failures from the outside inward
- Quinzee Internals: Testing and verification · Primary reference
- Quinzee Internals: The compatibility application · Primary reference