Native Jenkins
Works where you work.
Seamlessly integrate AI-powered Salesforce testing into your Jenkins Groovy pipelines. No external scripts required.
Groovy Native.
Our official Jenkins plugin exposes a native pipeline step, allowing you to trigger tests and consume JUnit XML reports automatically.
Native Pipeline Step
Use the simpletest() step directly in your Jenkinsfile without complex bash scripting.
JUnit Report Parsing
Results are automatically parsed by Jenkins' native test result analyzer for historical trends.
Credential Management
Securely retrieve API keys via the native Jenkins Credentials Provider.
pipeline {
agent any
stages {
stage('Run SimpleTest') {
steps {
simpletest
suiteId: 'regression',
credentialsId: 'simpletest-api-key',
waitForCompletion: true
}
}
}
post {
always {
junit 'target/simpletest-reports/*.xml'
}
}
}
How to connect with Jenkins
Get up and running in minutes with our turnkey integration. No complex setup or maintenance required.
Generate API Key
Log into your SimpleTest dashboard, navigate to Settings > API Keys, and generate a new key with CI/CD permissions.
Install Jenkins Integration
Install the native SimpleTest plugin/app from the Jenkins marketplace or add our CLI package to your pipeline.
Configure & Run
Add your API Key to your environment variables and point the integration to your specific Salesforce test suite ID.
Connected Jenkins execution.
Watch the Jenkins plugin connect, run Salesforce object paths from the pipeline step, and fail the build if any path breaks. JUnit results post back to the job.
Test Cases
Test execution
Waiting for run
0%
Starting
Frequently Asked Questions
Ready to supercharge your Jenkins pipeline?
Stop waiting for overnight tests and start shipping Salesforce releases with confidence. Set up the Jenkins integration today.
SimpleTest, defined.
SimpleTest sits in the pipeline you already run. Salesforce UI journeys become a required check — same as application tests.
What we address
What we address
- Salesforce ships outside CICode is gated. Metadata and Lightning changes still wait for a UAT window.
- Broken journeys after deployGearset, AutoRABIT, and GitHub ship the org. Nobody re-ran the quote or intake path.
- Results live in another toolQA has a report. Engineering has a PR. Failures do not block the merge.
- Scratch orgs and sandboxes driftEphemeral URLs and data never make it into the test run automatically.
What you get
What you get
- Native pipeline gatesGitHub Actions, Jenkins, Azure DevOps, ModernOps, Gearset, and AutoRABIT.
- Required status on the PRA failed Salesforce journey blocks merge the same way a failed unit test does.
- Jira when it failsDefects open with steps, org, and screenshot — not a Slack screenshot.
- Environment injectionScratch org and sandbox URLs flow into the suite. No manual re-pointing.
Everything in SimpleTest.
Generation, data, recording, parallel runs, self-healing, and CI gates — one product, every Salesforce release.