Testing your deploys takes two pieces. Your pipeline notifies QA Wolf that you deployed, and a trigger decides which flows run. The pages below cover the first piece.
Notify QA Wolf of your deploys
Pick the one that matches where your code lives and how you deploy.
- PR testing — what testing every pull request needs, on any of the paths below.
- GitHub — your repositories are on GitHub and something creates a deployment for each deploy, whether your own workflow or a provider such as Vercel.
- GitLab — your repositories are on GitLab and your pipeline’s deploy job declares an
environment:.
- Webhook — your code host is not GitHub or GitLab, or the deploy happens somewhere your code host never sees, so the pipeline notifies QA Wolf directly.
- Node.js SDK — the same notification from a pipeline that runs Node.js, such as Jenkins, with the option to block the pipeline on the verdict.
- CircleCI — you deploy from CircleCI, with the job and the environment variables it needs.
Mobile build testing is its own path: your pipeline uploads a build rather than notifying QA Wolf of a URL.
Still on legacy triggers
A workspace whose deploys are wired up the older way is documented under Legacy triggers. Last modified on October 5, 2026
