TestKase
TestKase|Docs
Test ManagementAutomationCI/CD Platforms

GitLab CI

Set up TestKase test reporting in your GitLab CI pipelines.

GitLab CI

GitLab CIGitLab CI

Setup Steps

  1. Go to your GitLab project → Settings → CI/CD → Variables. Add TESTKASE_PAT (masked).
  2. Add the reporting stage to your .gitlab-ci.yml.
  3. Update the CLI flags to match your project.
  4. Push to trigger your pipeline.

Pipeline Template

stages:
  - test
  - report

test:
  stage: test
  image: node:20
  script:
    - npm ci
    - npm test -- --reporter=junit --outputFile=test-results/junit.xml
  artifacts:
    paths:
      - test-results/
    when: always
  allow_failure: true

report-to-testkase:
  stage: report
  image: node:20
  when: always
  dependencies:
    - test
  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 "$CI_PIPELINE_IID"

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 is optional. If not provided, results are reported to TCYCLE-1 — the master test cycle for the project.

GitHub Actions

Set up TestKase test reporting in your GitHub Actions workflows.

Jenkins

Set up TestKase test reporting in your Jenkins pipelines.

On this page

GitLab CISetup StepsPipeline Template