CI/CD integrations let you trigger automated test runs from Qase and pipe the results back, no manual result entry required.
The pattern is the same regardless of which CI tool you use:
Configure a Qase reporter in your test framework.
Connect your CI pipeline to Qase so runs can be triggered from the UI.
Results flow back automatically as the pipeline executes.
The Shared Pattern
1. Set up a Qase reporter
Reporters are framework-specific libraries that send test results to Qase. See the developer documentation.
2. Connect the CI tool
Install the integration from the Apps page in your Qase workspace.
3. Run from Qase
Start an Automated test run from the Test Runs page. Select your CI tool, choose the pipeline/job, and Qase sends the trigger.
Supported CI/CD Tools
Tool | How it connects |
GitHub | GitHub App installation with repository access authorization |
GitLab | Personal Access Token via Qase GitLab app integration |
Jenkins | Jenkins API token via Qase plugin |
Bitbucket Pipelines | Atlassian Marketplace app (Qase for Bitbucket) |
For CI tools not listed here, configure a reporter in your test framework. The reporter sends results via the Qase API.
FAQ
Do I need both a reporter and a CI integration?
The reporter sends results. The CI integration lets you trigger runs from Qase. You can use a reporter without a CI integration.
Can I mix automated and manual results in the same run?
Yes.