Executions in QaCockpit for Azure DevOps

QaCockpit for Azure DevOps documentation

These guides cover the public Azure DevOps Marketplace extension, its current permissions, personal storage, evidence boundaries, and supported environment.

Looking for QaCockpit Cloud documentation?

Keep provider state and test evidence separate

Pipeline

Lifecycle

Queued, running, completed, canceled, or another provider state.

Evidence

Result intake

Complete, partial, missing, invalid, or still expected.

Tests

Outcome

Passed, failed, skipped, error, or unknown in the observed report.

Scope

Completeness

Published results and reported gaps or read limits for the selected execution.

Run and cancel actions require the relevant native pipeline permissions. The observed test count alone does not prove that every intended test ran. Historical evidence depends on Azure DevOps permissions and retention.

QaCockpit Test Executions in Azure DevOps showing monitored Test Sources, passing and failing evidence, missing reports, failed-test rankings, and slow executions. — Test Executions separates the latest usable report from failing, missing, or incomplete evidence for each monitored source.