Seamless CI/CD Pipeline Integration
Add a single npx command after your test step and results flow to TestKase automatically — tagged with build IDs, attached with artifacts, and visible in your dashboard within seconds.
First-Class Support for Every Major Pipeline
GitHub Actions, Azure DevOps, Jenkins, GitLab CI, Travis CI, Bitbucket Pipelines, CircleCI — and any platform that runs Node.js.
From Pipeline to Dashboard Automatically
Configure once, report on every build. Results flow to TestKase with zero manual intervention.
One-Line Integration
A single npx @testkase/reporter report command is all you need. Add it as a post-test step and you're done — no plugins or marketplace installs.
Build-Aware Results
Tag every result with --build-id to track which pipeline run produced which results. GitHub run number, GitLab pipeline IID, Jenkins build number — all supported.
Always-Run Support
Use continue-on-error (GitHub), when: always (GitLab), post { always } (Jenkins), or condition: always() (Azure) — results report even when tests fail.
Secret Management
Store your TestKase PAT as a pipeline secret. GitHub Secrets, GitLab CI Variables, Jenkins Credentials, Azure Pipeline Variables — all work natively.
Parallel Execution
Multiple parallel jobs can report to the same test cycle. Each job uploads its own results — TestKase merges them into a unified execution view.
No Plugins Required
Pure CLI-based integration. No marketplace plugins, no runner extensions, no Docker images. Works on any runner that has Node.js installed.
Copy-Paste Pipeline Snippets
Select your CI/CD platform below. Each snippet is production-ready — just update the flags with your project details.
GitHub Actions — Setup
Follow these 4 steps to integrate TestKase reporting into your GitHub Actions pipeline.
Add Secret
Go to your GitHub repo → Settings → Secrets and variables → Actions. Add TESTKASE_PAT with your personal access token.
Create Workflow YAML
Create .github/workflows/testkase-report.yml in your repository with the report step.
Update Flags
Replace --project-id, --org-id, --cycle-id, and --format with your actual values.
Push
Commit and push. The workflow triggers on push to main/develop and on pull requests.
name: Test & Report to TestKase
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
jobs:
test-and-report:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 20
- run: npm ci
- name: Run tests
run: npm test -- --reporter=junit \
--outputFile=test-results/junit.xml
continue-on-error: true
- name: Report results to TestKase
if: always()
run: |
npx @testkase/reporter report \
--token ${{ secrets.TESTKASE_PAT }} \
--project-id PRJ-1 \
--org-id 1173 \
--cycle-id TCYCLE-5 \
--format junit \
--results-file test-results/junit.xml \
--build-id "${{ github.run_number }}"Built for Pipelines
TestKase CI/CD integration is designed from the ground up for automated pipelines — zero manual steps, zero plugins, zero friction.
Best For These Teams
DevOps-First Teams
Teams that live in pipelines and need test results flowing into their QA dashboard without manual reporting.
Continuous Testing
Organizations running tests on every push, every PR, every merge — with results automatically tracked and trended.
Multi-Framework Shops
Teams using different frameworks across services. One reporter CLI handles Playwright, Cypress, JUnit, TestNG, and more.
Compliance & Audit
Regulated teams needing build-tagged test evidence. Every execution is tied to a specific build number for audit traceability.
Start Testing for Free
Sign up instantly and begin using TestKase with all core features, completely free for up to 3 users.