QaCockpit for Azure DevOps

Azure DevOps test reporting across projects and pipelines.

Choose the pipelines and Test Sources that matter to you, see where pipeline time and test evidence go, and follow every signal back to its exact Azure DevOps run. QaCockpit organizes the picture; your team decides what it means.

Install from Azure DevOps Marketplace View documentation

Installed for the organization, hidden by default. After installation, enable QaCockpit only for yourself in User settings > Preview features, or let an administrator enable it for the organization.

QaCockpit Quality Board in Azure DevOps showing project, pipeline, test, private-view, campaign, and failing-test summaries. — Quality Board keeps private views and campaigns above the Azure project inventory and current test evidence.

Free release visibility check

How clear is your release picture?

Check how your team brings results together, notices missing evidence and makes release decisions. Get practical next steps, with no account or email required.

Take the check →

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.

Stay in context

Work inside Azure DevOps

Use QaCockpit without creating a separate Cloud workspace for the normal extension workflow.

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

Viewing evidence does not grant pipeline commands. Queue and Stop use your native Azure permissions and require the disclosed vso.build_execute extension scope.

Pipeline Intelligence

See where pipeline time goes and where evidence is missing.

Review the available retained history for 7, 14, or 30 days. Overview uses all branches queued in the selected window. Performance uses completed default-branch runs and keeps run time, queue wait, and feedback time separate.

QaCockpit Pipeline Intelligence Performance showing run time, queue wait, feedback time, daily trends, queue share, and pipeline medians. — Performance highlights daily timing patterns and bounded rankings, then opens the exact Azure run behind a signal.

Overview

Start with the portfolio

Review active pipelines, outcomes, report completeness, operational signals, and daily activity across accessible projects.

Pipelines

Inspect one definition

Filter definitions, review their current state, and open the exact failure or source context available to you.

Evidence

Keep report state explicit

Distinguish complete, partial, missing, and unavailable test evidence instead of treating a completed pipeline as proof.

Performance

Separate time from outcome

Compare run and queue trends, pipeline medians, and exact-run stage, job, task, and anonymized concurrency facts.

QaCockpit Pipeline Intelligence Overview showing cross-project pipeline activity, failures, evidence completeness, actionable signals, and daily trends. — Overview connects cross-project signals to the pipeline, run, branch, commit, and test evidence that produced them.

Read the Pipeline Intelligence guide for metric boundaries, exact-run drill-down, permissions, and unavailable states.

Connected drill-down

Start with the quality picture. Drill down to the evidence.

QaCockpit points to failures, stale results, and missing evidence without replacing the scope and release decisions owned by your team.

Quality Board OverviewPrioritize projects by health, freshness, and missing evidence, then open recent executions and private reports.
Pipeline IntelligenceReview operational state, timing, and report completeness across the selected window.
Test Source and executionOpen the exact pipeline context and reported result set.
EvidenceInspect the test outcome, failure detail, history, and retained diagnostics.

QaCockpit My views in Azure DevOps showing private cross-project pipeline groups, current failures, evidence coverage, duration, and latest activity. — My views groups the pipelines you choose without changing their Azure DevOps projects, permissions, or run history.

Regression campaigns

Coordinate regression and release testing across pipelines.

A release may depend on UI, API, integration, and other suites owned by different pipelines. My campaigns saves your private source selection and prepares reports from exact executions in accessible projects of the same organization.

Use completed executions by default and choose Run pipeline only when new results are needed. Configure execution dependencies in Azure Pipelines.

Read how regression campaigns work

QaCockpit My campaigns overview in Azure DevOps showing private campaign health, recent reports, failed tests, and items requiring attention. — My campaigns keeps reusable source collections and their reports private to the signed-in user.

Available test history

Explore the evidence behind repeated test outcomes.

Review outcomes within your selected analysis window. Historical evidence depends on Azure DevOps permissions and retention.

Failure Inbox

Keep recurring failures in an investigation workspace.

Review currently failing tests, your private Status, Classification and Owner, and the available execution evidence.

Test Catalog

Explore tests observed in your selected sources.

Compare available outcomes in the analysis window. Renamed tests and different implementations are not automatically merged.

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 gap

One honest signal

Selected sources beside reported results

See which selected sources have reported results. Source-report completeness does not establish that every expected suite, shard or test was executed.

Initial Marketplace access

60 days free for each Azure DevOps organization.

The initial release starts with a 60-day organization evaluation. No payment method is required and it does not renew automatically. The end date is fixed when the evaluation starts, even if the default term changes for new organizations.

Paid sales will be enabled later at the planned $49 per Azure DevOps organization per month. QaCockpit Cloud remains a separate product with separate pricing.

Read billing and subscription answers

Included at launch

60-day evaluation · no card · no per-seat fee

The extension shows the exact evaluation end date. Paddle checkout, automatic renewal and billing management stay disabled until paid sales are enabled.

Common questions

Know the product boundary before installation.

Will everyone see QaCockpit after installation?

No. Azure DevOps installs the extension for the organization, but QaCockpit access is off by default. You can enable it only for yourself in User settings > Preview features; an administrator can separately enable it for the organization.

Does QaCockpit decide whether a release is ready?

No. QaCockpit organizes the evidence available in Azure DevOps, highlights failures and evidence gaps, and keeps summaries connected to exact runs. Your team chooses the scope and makes the release decision.

Do we need a QaCockpit Cloud workspace?

No. The normal Marketplace extension workflow runs inside Azure DevOps. QaCockpit Cloud is a separate hosted edition for organizations that need one layer across GitHub Actions and Azure DevOps.

Are views, campaigns, and failure investigation details shared?

No in the first public release. My views, My campaigns, report records, and Failure Inbox Status, Classification, and Owner are private to the signed-in user.

Does QaCockpit run our tests?

Azure Pipelines and your existing frameworks continue to run the tests. QaCockpit reads the evidence available to the signed-in user and can send an explicit Queue or Stop request only when that user has the required Azure permission.

Which permissions does Pipeline Intelligence use?

Pipeline Intelligence uses read-only Code, Analytics, and Agent Pools scopes together with the signed-in user's Azure permissions. They support exact-commit YAML location, bounded timing facts, and aggregate anonymized capacity views. Existing installations require an organization administrator to authorize the new scopes before upgrading to version 1.1.0.

What is included in the initial Marketplace access?

Each Azure DevOps organization can start a fixed 60-day evaluation without a payment method or automatic renewal. Paid sales are planned separately at USD 49 per organization per month.

Read the complete Azure DevOps extension FAQ or review permissions and data handling.

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 Services at dev.azure.com
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.