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
Start from authorized Azure DevOps context
After installation, open QaCockpit from the contribution documented for the stable build. The extension must respect both its manifest scopes and the signed-in user's Azure DevOps permissions. Project discovery and cross-project visibility must never bypass that effective access.
02
Connect the first evidence path
- Choose an authorized project or organization context.
- Review the pipelines and result streams the extension actually discovers.
- Select one release-relevant Test Source.
- Confirm how that source exposes structured test results and diagnostics.
- Open the first execution and trace its signal back to Azure DevOps.
Exact button names and discovery rules will be published after the stable build is certified. The flow will not copy the QaCockpit Cloud provider connection process.
03
Validate the result, not only the navigation
- The pipeline identity, branch, commit, and attempt match the Azure DevOps run.
- Pipeline lifecycle and test outcome appear as separate facts.
- A missing or partial result is visible rather than silently treated as passed.
- The user can drill from the cockpit to the exact source and execution evidence.
- A user without access receives a clear, non-leaking permission state.
