Full Service customers: Smart Smoke Suites run as part of PR testing. Talk to your QA Wolf team to turn them on.
How it works
- 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.
- The agent compares the change with your existing flows, along with any instructions on the trigger, and picks the flows the change affects.
- The selected flows run against the deploy’s URL.
- 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 deploy tied to a pull request. It can go to any environment, not only a preview. GitHub deployments and GitLab deployment jobs are tied automatically. A
deployment.reportStatusreport is tied when it sendsmetadata.repositorywithmetadata.pullRequestNumber, or withmetadata.commitShawhile that pull request is still open. See Deployments. - A deployment trigger matching those deploys. On the triggers page, start it from Pull request previews, enter the environment name pattern, such as
pr-*, and pick Let QA Wolf choose from the pull request’s changes. The pattern isn’t limited to previews, sodev-*covers several static dev environments. The triggers table shows the trigger as Smart smoke suite.
generativeSuite; see Trigger fields. It needs PR testing: a deploy with no pull request behind it, such as a merge to main deployed to staging, is skipped.