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?01
Name the failing boundary
- Did Azure DevOps create and complete the expected pipeline run?
- Did the test command execute the intended suite or shard?
- Did the pipeline publish structured results or retain the required file?
- Could the extension discover and read that exact result through its verified path?
- Did the complete expected scope arrive, and what was the test outcome?
02
When a pipeline succeeds but evidence is missing
- Confirm the expected pipeline, branch, commit, and attempt.
- Inspect whether the test command ran or was skipped by a condition.
- Confirm the result file is non-empty and uses the supported format.
- Check whether publication/retention runs even after failed tests.
- Compare reported tests with the scope agreed by your team; the current extension does not establish a full expected-test baseline.
- Check Azure Test results first, then compatible retained JUnit artifacts and any read-limit warnings shown in Diagnostics.
03
When projects or pipelines are unavailable
Confirm that the extension requests the expected manifest scopes and the current user has effective access to the target resource. Test with a limited identity; do not grant broad permissions merely to hide a partial-access bug.
04
Collect safe support evidence
Record the extension version, sanitized organization/project context, pipeline or test-run identifiers, timestamps, expected and observed state, and a screenshot of the visible error. Never send tokens, cookies, PATs, secrets, private source, or raw customer payloads.