Skip to main content

​
Features

These features require providing specific parameters to deploy_success. See Deploy Success Webhook - With GitHub/GitLab app installed.

​
Commit Status

You will find a status badge associated with the run
Commit status screenshot from GitHub integration.

​
PR Comment

A detailed comment will show up and update automatically. Each run for every tested commit will show up in a row.
At the top right of the run page, you will find a link to the commit associated with the deployment being tested.
The branch name and commit link in a QA Wolf run page

​
Setup

​
Trigger Setup

These steps require assistance from a QA Wolf representative.
First, you will need to reach out to your QA Lead/QA Manager and get a trigger setup to track your deployments. Once your trigger is setup, press the Edit “trigger name here” button to view the screen below, and click connect code hosting service
This will redirect you to your settings page where you can enable the GitHub or GitLab integration for your team. Click enable and then follow the process below to enable your GitHub or GitLab integration

​
For GitHub

These steps require assistance from a QA Wolf representative.
Click the change repositories button:
This will open a new page that will allow you to select the repositories you would like to integrate with our application
Choose the repo(s) you want to test and click the green Install button. After the installation succeeds, the new tab will close. Confirm the repo you want to test is now selected in the dropdown.
When you push a commit to GitHub, your tests will run after your deployment succeeds.
QA Wolf will comment on a pull request with the most recent test suite. As your tests run, the comment is updated to report the latest results.

​
For GitLab

These steps require assistance from a QA Wolf representative.
GitLab integration is still experimental. We recommend contacting a QA Wolf representative before enabling it.
After you click the enable button next to the GitLab integration you will be met with the following screen. To integrate with our platform you will have to create a group access token with the Maintainer role and API privileges.
The Maintainer Role is required because the Developer Role doesn’t have enough permissions if the branch is protected, preventing us from creating pipeline checks.
You can follow this tutorial on the GitLab website to create this token. Once the token is created go ahead and paste it into the input shown below.
After creating your token and linking it with our platform, navigate back to your trigger, press the edit button, and select the GitLab repository that you would like this trigger to provide PR comments and commit status updates to.
After you make a call to the `deploy_success` endpoint with the `branch` and `sha` of your merge request, you should see a comment that allows you to track the status of the suite for your merge request
Merge request comment screenshot of the integration
Along with the merge request comment, there will be a pipeline status created tracking whether or not your tests passed.
Commit status screenshot of the integration

​
Notes on Multi-Repositories

There are two options for multi-repositories setups: Using a GitHub/GitLab App installation per repository. This require setting up one trigger per repository. Leveraging a job in your CI pipeline to use our @qawolf/ci-sdk - pollCiGreenlightStatus helper, or the CI Greenlight HTTP endpoint directly.
Last modified on February 9, 2026