Stay in context
Work inside Azure DevOps
Use QaCockpit without creating a separate Cloud workspace for the normal extension workflow.
QaCockpit for Azure DevOps
See quality across Azure DevOps projects and pipelines.
Bring pipeline test evidence, project health, campaigns, and recurring failures into one quality cockpit inside Azure DevOps—without moving your engineering workflow to another platform.
Coming soon to Azure DevOps MarketplaceView documentation
Organization Cockpit preview
Azure-native experience
Built for teams that live in Azure DevOps.
The Marketplace edition is designed for organizations that want the quality picture where their projects and pipelines already live.
See the organization
Stop opening pipelines one by one
Start with projects that need attention, then follow the signal to its exact source and execution.
Keep execution
Your pipelines stay the source of truth
QaCockpit organizes quality evidence; it does not replace Azure Pipelines or your test frameworks.
Respect access
Make permissions visible
Final scopes, access behavior, storage, and network boundaries will be published from the certified extension build.
Connected drill-down
Start with the quality picture. Drill down to the evidence.
Management visibility stays connected to the execution details engineers need.
- Organization CockpitPrioritize projects by health, freshness, and missing evidence.
- Project CockpitUnderstand source health, current failures, and regression state.
- Test Source and executionOpen the exact pipeline context and reported result set.
- EvidenceInspect the test outcome, failure detail, history, and retained diagnostics.
Regression campaigns
Coordinate regression and release testing across pipelines.
A release may depend on UI, API, integration, and other suites owned by different pipelines. Campaigns define the required Test Sources, preserve each attempt, and show which evidence reported, failed, or never arrived.
Sequential stages and parallel work within a stage keep the model understandable without turning QaCockpit into another workflow engine.
Read how regression campaigns work
Durable quality history
A pipeline ends. The quality history shouldn't.
Move recurring evidence out of isolated run pages and into focused operational views.
Failure Inbox
Turn repeated failures into owned investigation.
Group recurring failures, preserve triage context, and keep the path back to exact evidence.
Test Catalog
Keep test identity and history beyond one run.
Follow a logical test across implementations and executions to understand current and repeated signals.Evidence completeness
Green isn't enough when evidence is missing.
Pipeline completion, test execution, result publication, result intake, and test outcome are different facts. QaCockpit keeps them separate so a successful pipeline with a missing or partial report cannot masquerade as complete evidence.
Understand the evidence gapOne honest signal
Expected scope beside observed results
See what the release intended to collect, what actually reported, and where a source, suite, shard, or result file is still missing.
Choose your edition
Choose the QaCockpit edition that fits your environment.
| Decision | QaCockpit Cloud | QaCockpit for Azure DevOps |
|---|---|---|
| Best for | Mixed CI/CD environments | Azure DevOps-centered organizations |
| Providers | GitHub Actions and Azure DevOps | Azure DevOps |
| Experience | Hosted QaCockpit web application | Inside Azure DevOps |
| Setup | Connect providers | Install the Marketplace extension |
| Cloud workspace | Used | Not required for the normal extension workflow |
| Primary value | Cross-provider quality intelligence | Azure-native quality intelligence |
Using GitHub Actions and Azure DevOps together? QaCockpit Cloud is designed for multi-provider environments. Explore the Cloud workflow.