Skip to main content
Testing your deploys takes two pieces. Your pipeline reports a deployment to QA Wolf, and a trigger decides which flows run for it. The pages below cover the first piece: how the report reaches QA Wolf from where you deploy.

​
Report your deploys

Pick the one that matches where your code lives and how you deploy.
  • 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 reports it directly.
  • 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 reporting a URL.

​
Connect the rest of your tooling

​
Still on legacy triggers

A workspace whose deploys are wired up the older way is documented under Legacy triggers.
Last modified on September 18, 2026