Azure DevOps
Set up TestKase test reporting in your Azure DevOps pipelines.
Azure DevOps
Azure DevOps
Setup Steps
- Go to your Azure pipeline → Edit → Variables. Add
TESTKASE_PAT(secret). - Add the reporting step to your
azure-pipelines.yml. - Update the CLI flags to match your project.
- Save and run.
Pipeline Template
trigger:
branches:
include:
- main
- develop
pool:
vmImage: 'ubuntu-latest'
steps:
- task: NodeTool@0
inputs:
versionSpec: '20.x'
- script: npm ci
displayName: 'Install dependencies'
- script: npm test -- --reporter=junit --outputFile=test-results/junit.xml
displayName: 'Run tests'
continueOnError: true
- script: |
npx @testkase/reporter report \
--token $(TESTKASE_PAT) \
--project-id PRJ-1 \
--org-id 1173 \
--cycle-id TCYCLE-5 \
--format junit \
--results-file test-results/junit.xml \
--build-id "$(Build.BuildNumber)"
displayName: 'Report to TestKase'
condition: always()npm test -- --reporter=junit --outputFile=… is a placeholder, not a real command for most runners.
Replace it with the command that produces your framework's results file — e.g.
pytest --junitxml=test-results/junit.xml, npx playwright test, or mvn test — and set --format
to match. See the Test Frameworks guides for the
exact command and format per framework.
--cycle-id TCYCLE-5 above is a placeholder. The test cases you report on must already be linked to
the cycle you target. If they are not, the API rejects every result with Test case not linked with
this test cycle, the reporter exits 1, and this pipeline goes red on its first run. Either add those
test cases to the cycle first, or drop --cycle-id altogether and report into TCYCLE-1 — the Master
Cycle, which always contains every test case in the project.