Testing Application Upgrades and Regressions
A developer wants to verify that a new application version will not break existing functionality.
Intermediate · Developer · 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
Local instances let you control inputs and service state while investigating an application change.
The proposed example
Run a fixed test dataset against two application versions in separate, inventoried environments and compare results.
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
- Keep the old application image and expected results.
- Recreate fixtures or use a rehearsed consistent restore; do not assume a snapshot/reset command exists.
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