Skip to content
Azure DevOps: not available today

Azure DevOps testing and verification evidence

Zof has no Azure DevOps connection today. Zof works with GitHub.

Who this is for

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.

  • Zof and Azure DevOps today

    Zof has no Azure DevOps connection today. Zof works with GitHub.

In your workflow

From a change to a review decision

  1. 01

    Choose the agent and scope

    Identify Azure DevOps Services or Server, the agent OS, repository revision and test environment.

  2. 02

    Run checks and collect reports

    Run your existing test command and preserve its exit status. Publish supported test results with Azure’s task.

  3. 03

    Retain and review evidence

    Keep original reports and the resulting 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 report file does not enforce a release gate.

Reviewable records

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 record

    Zof does not read Azure DevOps results today.

Prerequisites and limits

  • No 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.
  • Agent operating systems and runtimes must match what your deployment supports. Static verification does not execute application tests.
  • Your pipeline supplies the reports and their provenance. A well-formed report 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.