Azure DevOps testing and verification evidence
Plan how Azure Pipelines test results and Zof’s local verification evidence fit together, with clear prerequisites and integration limits.
Platform, engineering and QA teams using Azure Pipelines who need test evidence tied to a software change before approving its release.
What Zof does
Keep execution in your pipeline
Azure Pipelines runs jobs on your chosen agent. Microsoft’s Publish Test Results task presents supported results in Azure DevOps; artifact publishing retains selected files. These are Azure capabilities, not Zof connectors.
Evaluate local Zof tools
Zof is the independent verification and control layer between AI and production. Its released CLI performs local static checks; CI Evidence normalizes selected local reports. Both can be evaluated as commands within an approved agent environment.
From a change to a review decision
- 01
Choose the agent and scope
Identify Azure DevOps Services or Server, the agent OS, repository revision and test environment. Provision the supported Zof runtime and dependencies through your approved installation process.
- 02
Run checks and collect reports
Run your existing test command and preserve its exit status. Publish supported test results with Azure’s task. Evaluate Zof’s local checks and report normalization separately before making them a pipeline requirement.
- 03
Retain and review evidence
Keep original reports and normalized evidence with the job and commit record. Configure handling for failed tests, missing reports and publishing errors. Map the result to your existing approval process; a JSON file does not enforce a release gate.
What evidence you get
Azure test and artifact records
Azure’s test publisher accepts formats including JUnit and TRX. Artifact availability and retention depend on your pipeline and Azure edition. Confirm the relevant tasks for Services or Server.
Zof’s local record
CI Evidence 0.1.1 accepts its documented JUnit subset, generic test JSON and static-analysis JSON. It records outcomes and completeness; selected file imports include relative references, sizes and SHA-256 hashes. It does not accept TRX directly.
Prerequisites and limits
- No released Zof Azure DevOps extension, work-item synchronization or hosted release-gate integration is verified here. This is a workflow evaluation guide, not an accepted Azure pipeline configuration.
- Local Zof file operations require Node.js 22 or 24, Linux or macOS, and Python 3.10 or newer. Windows file operations fail closed. Static verification does not execute application tests.
- Report normalization neither downloads Azure artifacts nor uses Azure credentials. Your pipeline supplies trusted local files and provenance. Schema validity and a file hash do not authenticate the test run.
- A self-hosted agent is not automatically air-gapped. Review its Azure connection, package downloads, test targets and artifact destinations. Hosted Zof functionality requires separate validation.
Validate one pipeline before rollout
Bring the pipeline definition, agent environment, sample report formats and approval requirements to a technical review. Confirm local command behavior and the required hosted integration scope.