QA.tech + GitHub Actions
The GitHub Actions integration lets you trigger a specific QA.tech test plan from a workflow step via the REST API. You pass preview URLs between jobs, gate merges on a chosen plan, and kick off AI change reviews from your own pipeline steps. It's the scripted counterpart to the GitHub App: you decide exactly when and what runs.
What you can do
- Run a smoke or critical-path plan on every deploy
- Gate merges on a chosen test plan
- Test dynamic preview URLs passed between jobs
- Trigger AI change reviews from your own pipeline steps
Set it up
Connecting GitHub Actions
- 01
Copy the Short ID of the test plan you want to trigger.
- 02
Add an API key as a repository secret and call the trigger endpoint from a workflow step.
- 03
Pass the preview URL from the deploy job as an application or environment URL override.
- 04
Full walkthrough in our step-by-step GitHub Actions guide.
Full reference in the QA.tech docs.
Where teams use this
GitHub Actions in practice
This is the manual-control route into PR and CI/CD testing. Use the App for automatic PR coverage and Actions for control: teams typically gate merges on a smoke plan and run a critical-path regression plan on deploys to staging. Because URLs are passed at trigger time, the same plan tests whatever preview or staging environment the pipeline just built.
FAQ
Common questions
- App or Actions: which one do I need?
- The App for automatic reviews on every PR; Actions when you want to choose the plan, the timing, and the target URL yourself. Most teams run both.
- Can I test a different URL per run?
- Yes, application and environment URLs are overridden at trigger time.
Related integrations
GitHub App
Next →GitLab
Your team moves fast. Can your testing keep up?
QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.