Skip to main content
A Smart Smoke Suite is one way for a trigger to choose its flows. Instead of running flows you name in advance, the QA Wolf agent selects the flows affected by the pull request behind each deploy. This gives engineers a faster release signal in the review cycle. Smart Smoke Suites are designed to layer onto your existing coverage strategies. The suite has no fixed size. The agent selects the flows it judges affected by the change, so a wide-ranging PR selects more flows than a narrow one. It can also be empty: when the agent judges a change low-risk, or finds no flow that covers it, no run starts.
Smart Smoke Suites are currently in alpha and not available to all customers. Early customers running it in production work closely with QA Wolf to validate the experience and tune selection quality.

​
How it works

  1. QA Wolf reads the pull request behind the deploy: its title and description, plus its changed files and diff on GitHub. On GitLab it reads the merge request’s title and description only.
  2. The agent compares the change with your existing flows, along with any instructions on the trigger, and picks the flows the change affects.
  3. The selected flows run against the deploy’s URL.
  4. QA Wolf posts the agent’s analysis as a comment on the pull request, and reports the result on the pull request as described in PR testing. When no run starts, GitHub gets a passing QA Wolf Test Results check.

​
Requirements

  • A connected GitHub or GitLab integration covering the deploying repository, so each deploy links to its pull request. See PR testing.
  • A preview deploy per pull request, reported through GitHub deployments, a GitLab deployment job, or deployment.reportStatus.
  • A deployment trigger whose flows are set to Generative suite on the triggers page.
Once it’s set up, each preview deploy linked to a pull request gets its own selection. To stop, switch the trigger back to Flows with selected tags, or pause it. The change applies to deploys that arrive afterwards. A Smart Smoke Suite is a deployment trigger whose action kind is generativeSuite; see Trigger fields. It needs PR testing: a deploy that is not linked to a pull request is skipped.

​
FAQ

​
How does QA Wolf decide which flows to run?

The agent reads the pull request (its title and description, and on GitHub its changed files and diff), your existing flows, and any instructions on the trigger. It picks the flows it judges the change affects.

​
Can we add specific tests to always run on PRs?

Name them in the trigger’s instructions. Instructions guide the agent’s selection; they don’t guarantee a flow runs.

​
Do we have to write new flows specifically for Smart Smoke Suites?

No. The agent selects from the flows you already have.
Last modified on October 15, 2026