CircleCI

Setup Steps

Go to your CircleCI project → Project Settings → Environment Variables. Add TESTKASE_PAT.
Add the reporting step to your .circleci/config.yml.
Update the CLI flags to match your project.
Commit and push to trigger.

Pipeline Template

version: 2.1

jobs:
  test-and-report:
    docker:
      - image: cimg/node:20.0
    steps:
      - checkout
      - run:
          name: Install dependencies
          command: npm ci
      - run:
          name: Run tests
          command: npm test -- --reporter=junit --outputFile=test-results/junit.xml
          when: always
      - store_test_results:
          path: test-results
      - run:
          name: Report to TestKase
          command: |
            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 "$CIRCLE_BUILD_NUM"
          when: always

workflows:
  test:
    jobs:
      - test-and-report

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.

CircleCI

CircleCI

CircleCI

Setup Steps

Pipeline Template

On this page