Native GitHub Actions
Works where you work.
Trigger 10,000 parallel Salesforce tests directly from your GitHub PRs. Block merges automatically if regressions are detected.
Test every commit.
By integrating SimpleTest natively as a GitHub Action, you bring Salesforce testing into the same workflow your developers already use for application code.
PR Status Checks
Results post directly back to the GitHub PR as a required status check.
One-Line Integration
Just use the simpletest-ai/action block and pass your API key.
Environment Injection
Automatically pass ephemeral scratch org URLs into the test runner.
name: Salesforce Regression
on:
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- name: Run SimpleTest Suite
uses: simpletest-ai/action@v2
with:
api-key: ${{ secrets.ST_API_KEY }}
suite-id: "sf-core"
block-pr: true
How to connect with GitHub Actions
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 GitHub Actions Integration
Install the native SimpleTest plugin/app from the GitHub Actions 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 GitHub execution.
Watch the GitHub App connect, run Salesforce object paths on the pull request, and post a required status check. The merge stays blocked until every path passes.
Test Cases
Test execution
Waiting for run
0%
Starting
Frequently Asked Questions
Ready to supercharge your GitHub Actions pipeline?
Stop waiting for overnight tests and start shipping Salesforce releases with confidence. Set up the GitHub Actions 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.