This guide is for QA Wolf full service customers. If you’re unsure whether this applies to you, contact your QA Wolf team.
Configure basic PR testing
1
Configure GitLab integration
Configure the GitLab integration in your team’s settings page.
2
Notify QA Wolf of preview deployments
Choose one of the following methods to tell QA Wolf when a new preview environment is ready to be tested.GitLab CI jobAdd a curlIf Node isn’t available in your pipeline, you can notify QA Wolf using a raw HTTP call instead.
notify_qawolf job to your .gitlab-ci.yml that runs only for merge request pipelines, after the preview environment is deployed and reachable.What this job assumes
- Your pipeline already creates a preview environment for each merge request.
- The preview environment URL is available as
PREVIEW_URLwhen this job runs. - A prior job (such as
deploy_preview) deploys the preview environment and verifies it is reachable before notifying QA Wolf.
3
Ask your QA Wolf team to set up triggers
QA Wolf will configure a trigger that matches your preview deployments. Reach out to your QA Wolf team to get this set up.
Advanced: Require QA Wolf tests before merge
In GitLab, merge requests are typically blocked unless pipelines pass. Complete this section if you want to enforce QA Wolf results as a required check.
Verify your PR testing setup
1
Open a merge request in GitLab.
Confirm that your merge request triggers a pipeline that deploys a preview environment.
2
Confirm the preview environment is created.
In GitLab, check the merge request’s environment or the Review App link, and confirm that the preview URL is reachable.
3
Confirm QA Wolf starts a test run.
In the QA Wolf app, go to the Runs tab and verify that a new run starts for the preview environment associated with the merge request.
4
Confirm the merge request is blocked on failure.
In GitLab, confirm the pipeline reflects the final result and that the merge request cannot be merged unless the pipeline succeeds.