Marketplace release in final preparation
These guides cover the release candidate, including its current permissions, personal storage, evidence boundaries, and supported environment. The public install action stays disabled until the listing is live.
Looking for QaCockpit Cloud documentation?01
Private launch candidate
The package remains private while final screenshots and public Marketplace approval are completed. This page describes the customer-visible contract prepared for launch.
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
QaCockpit organizes evidence; your team makes the decision
Users choose the Test Sources they monitor, the pipelines in each view, and the exact executions included in a campaign report. QaCockpit connects those choices to current outcomes, failures, freshness, and missing or partial evidence.
The extension does not automatically certify release readiness, approve a release, infer a complete expected-test baseline, or replace dependencies configured in Azure Pipelines.
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.