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
Use the smallest verified scope
Azure DevOps extension access is constrained by both manifest scopes and the signed-in user's effective permissions. Every requested scope must map to a shipped read or command. Queueing, canceling, or changing pipeline state must be assessed separately from read-only visibility.
The stable listing must expose its requested scopes before install. High-privilege scopes require an explicit product need, security review, customer explanation, and release evidence.
02
Answers required from the stable build
Read and command access
Exact manifest scopes, resources read, and any run/start/cancel operations.
Current-user behavior
How project access, cross-project visibility, and denied resources are enforced.
Configuration and evidence
Which data uses Extension Data or another store, its scope, retention, and removal behavior.
External calls
Every external origin and whether a QaCockpit-operated backend participates in normal use.
03
Fail closed when access is partial
A user without access to a project, pipeline, test run, or stored document must not receive names, counts, cached details, or links from that resource. The stable build needs two-user tests covering success, empty access, partial access, revoked access, and Extension Data conflict behavior before public launch.
Provider references:extension manifest and scopesand high-privilege extensions.