CI/CD Platforms

Overview

Integrate TestKase reporting into your CI/CD pipeline to automatically push test results after every build. Each platform guide provides a ready-to-use pipeline template with the @testkase/reporter CLI.

Supported Platforms

Platform	Guide
GitHub Actions	GitHub Actions Guide
GitLab CI	GitLab CI Guide
Jenkins	Jenkins Guide
Azure DevOps	Azure DevOps Guide
CircleCI	CircleCI Guide

Common Pattern

Every CI/CD integration follows the same three-step pattern:

Store secrets — Add TESTKASE_PAT as a CI/CD secret or environment variable. Never hardcode tokens in pipeline files.
Run tests with continue-on-error — Your test step should not block the pipeline on failure. Use continue-on-error: true (GitHub Actions), allow_failure: true (GitLab CI), or equivalent.
Run the reporter with always-execute — The reporting step must run regardless of test pass/fail. Use if: always() (GitHub Actions), when: always (GitLab CI), or post { always { } } (Jenkins).

Example Reporter Step

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_NUMBER"

--cycle-id is optional. If not provided, results are reported to TCYCLE-1 — the master test cycle for the project.

Always include --build-id with your CI build number. This links each execution to a specific build, making it easy to trace results back to code changes.

Next Steps

Choose your platform guide above and follow the step-by-step instructions.
See Best Practices & FAQ for troubleshooting and optimization tips.
See CLI Reference for the full list of reporter flags.