GitLab CI

Setup Steps

Go to your GitLab project → Settings → CI/CD → Variables. Add TESTKASE_PAT (masked).
Add the reporting stage to your .gitlab-ci.yml.
Update the CLI flags to match your project.
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 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.

GitLab CI

GitLab CI

GitLab CI

Setup Steps

Pipeline Template

On this page