Join our free walkthrough webinar on May 18 at 10 AM CEST or 11 AM EDT to learn more!
Integration

Run Automated Tests with Jenkins from Qase

Start Jenkins pipelines directly from Qase and connect automated results back to your test runs for end-to-end QA visibility.

Start trialGet a demo

No credit card required

Run Automated Tests with Jenkins from Qase
AsanaBitlyBumbleCrypto.comRakutenSeatGeekSUSEWolt
AsanaBitlyBumbleCrypto.comRakutenSeatGeekSUSEWolt

Bring CI/CD and Manual QA Together

Qase’s Jenkins integration lets teams orchestrate automated test execution without context-switching. Trigger Jenkins jobs from within Qase, observe pipeline progress and results alongside manual test runs, and capture automated outcomes back into your QA workflows, keeping the full picture in one place.

Qase Screenshot - Control System

What the Jenkins Integration Delivers

Trigger Jenkins jobs from QaseStart automated test pipelines right from the Qase Test Runs page. Select Jenkins as your CI system, choose the job you want to run, and execute without leaving Qase.

Qase Screenshot: Pytest code snippet

Why teams trust Qase

“The platform is intuitive, clear, and easy to work with, making test management smooth and efficient… Support[s] integration with Jenkins for CI/CD pipelines.”

Tal M. QA Testing & Automation

“The platform is intuitive, clear, and easy to work with, making test management smooth and efficient… Support[s] integration with Jenkins for CI/CD pipelines.”

Tal M. QA Testing & Automation

“The platform is intuitive, clear, and easy to work with, making test management smooth and efficient… Support[s] integration with Jenkins for CI/CD pipelines.”

Tal M. QA Testing & Automation

How it works

Loved by small and enterprise customers

Winter 2026 Leader
Fastest Implementation
Best Relationship Mid-Market
Users Love Us
Best Usability

FAQs

Yes. From a Qase test run you can choose Jenkins as the CI system, select a job, and start it directly.
Yes. Once a Jenkins job is triggered from Qase, you can monitor its status and see results in the Qase interface.
By configuring your Jenkins job with Qase reporter settings and environment variables, test execution results upload back to the corresponding run in Qase automatically.
You’ll need a valid Jenkins instance and an API token to connect it with Qase. Parameterizing your jobs to accept reporter variables lets results flow back into Qase.
Yes, both freestyle and pipeline jobs can be used to trigger automated runs and publish results to Qase with the reporter integration.

Ship quality software faster with Qase

Start trialGet a demo