Skip to main content
PR testing runs your flows against a pull request’s preview deploy and reports the result on the pull request. GitLab calls them merge requests; the feature is the same.

​
What it needs

  • A connected GitHub or GitLab integration covering the deploying repository. This is what ties a deploy to its pull request. Connect it under Workspace settings → Integrations; see GitHub or GitLab.
  • A preview deploy per pull request, with its own environment name and its own URL. Mark it as a preview so its environment is torn down when the pull request closes. See Deployments.
  • A deployment trigger matching those previews, such as preview/* or review/*. See Triggers.

​
Without a connected repository

A GitHub or GitLab deployment from a repository the integration doesn’t cover never reaches QA Wolf, so nothing runs. A deployment.reportStatus report is different. For a repository with no integration, it’s still accepted, triggers match, and the flows run against the preview. QA Wolf can’t link the deploy to a pull request or post checks, and a Smart Smoke Suite skips it with the reason no-pull-request. Nothing reports the missing checks. This is the path for Bitbucket, Azure DevOps and any other code host.

​
Checks on the pull request

On GitHub, QA Wolf posts two checks against the deployed commit:
  • QA Wolf Test Run — the run’s progress.
  • QA Wolf Test Results — the outcome.
On GitLab, it posts one commit status, QA Wolf Test Results. To gate merges on QA Wolf, require QA Wolf Test Results in your branch protection rules or ruleset. QA Wolf Test Run passes whenever the run finishes, so don’t require it.
A workspace still on legacy triggers is documented under PR testing on GitHub and PR testing on GitLab.
Last modified on October 15, 2026