This documentation covers the QaCockpit Azure DevOps Marketplace extension. Exact install labels, scopes, storage, and network behavior will be finalized from the certified release build.
Looking for QaCockpit Cloud documentation?01
Model the business regression, not one pipeline
A release may require browser, API, integration, and service-level validation owned by different teams. A Campaign names the required Test Sources so the final report can distinguish a complete regression from a collection with missing evidence.
02
Keep orchestration understandable
QaCockpit's Campaign model supports sequential stages and parallel work within a stage. It coordinates evidence across existing pipelines; Azure DevOps remains the execution system and QaCockpit does not become a general-purpose workflow engine.
- Use a template for a repeatable regression or release scope.
- Keep one-time collections explicit instead of silently changing a template.
- Preserve a separate execution attempt for every run or rerun.
- Do not collapse a missing source into the outcome of sources that reported.
03
Read outcome beside evidence completeness
A Campaign Run Report should show the fixed campaign context, reported test totals, failed/error outcomes, expected scope, source-report completeness, and the exact execution behind every signal. The stable extension must prove which Campaign create/run actions it exposes before those UI steps are published.