DocumentationExecutions

Executions in QaCockpit for Azure DevOps

An execution connects one Test Source and one provider run with its attempts, results, scope, and retained evidence.

Pre-launch Azure DevOps extension documentation

This documentation covers the QaCockpit Azure DevOps Marketplace extension. Exact install labels, scopes, storage, and network behavior will be finalized from the certified release build.

Looking for QaCockpit Cloud documentation?

01

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

Expected identities beside the tests and suites that actually reported.

Every rerun should create a new attempt. The stable extension must verify whether it can start or cancel provider runs and which manifest scopes those commands require.