These guides cover the public Azure DevOps Marketplace extension, its current permissions, personal storage, evidence boundaries, and supported environment.
Looking for QaCockpit Cloud documentation?01
Superseded private launch candidate
02
What is included
- Quality Board views for organization and project-level quality signals.
- Private My views for user-selected pipeline groups across accessible projects.
- Test Sources, Test Executions, Test Catalog, and Failure Inbox evidence.
- Private My campaigns and reports built from exact selected executions.
- Optional Queue and Stop actions that follow the signed-in user's Azure permissions.
- A fixed 60-day organization evaluation without a card or automatic renewal.
03
Bounded evidence, not an automatic certification
Test Catalog reconstructs logical-test history from the bounded Azure Test evidence available in the current session. Users choose monitored Test Sources, private views, and the exact executions included in campaign reports.
QaCockpit organizes current outcomes, failures, freshness, and missing or partial evidence. It does not certify release readiness, infer a complete expected-test baseline, or make the release decision for the team.
04
Access, privacy, and known limits
- Azure DevOps Services at
dev.azure.comis supported; Azure DevOps Server is not. - My views, My campaigns, reports, and Failure Inbox Status, Classification, and Owner are private to each user.
- Azure DevOps permissions and retention determine which execution evidence remains available.
- The narrow licensing service receives no pipeline names, project names, test names, results, or product-usage telemetry.
- Paid sales remain disabled until a separate commercial go-live; the planned later price is USD 49 per organization per month.
