Skip to main content
If your repositories are hosted on GitLab.com or on a GitLab Enterprise Server instance with internet access, this is the recommended setup. The integration connects directly to your QA Wolf environments.
If your GitLab instance does not allow outbound HTTPS connections (for example, an air-gapped GitLab Enterprise installation), use the QA Wolf CI SDK instead.
Make sure you have:
  • Admin or Maintainer access to the GitLab project.
  • Access to your QA Wolf workspace.
  • At least one QA Wolf environment already configured.
  • A QA Wolf API key.

Connect QA Wolf to GitLab

Enable the GitLab integration from Workspace Settings → Integrations in QA Wolf. You’ll be asked to provide a Group Access Token with the Maintainer role and API scope.
The Maintainer role is required because Developer tokens cannot create pipeline checks on protected branches.
Once connected, QA Wolf can set commit statuses and link test runs to GitLab commits.
1

Generate a QAWOLF_API_KEY

Generate a QAWOLF_API_KEY from Workspace Settings → Integrations → API Access.
2

Add it as a CI/CD variable

Add it as a QAWOLF_API_KEY CI/CD variable in your GitLab project under Settings → CI/CD → Variables. You can also define additional variables, such as a deployment URL, if your pipeline uses them.

Add the deploy notification to GitLab CI/CD

QA Wolf provides a public API endpoint that your GitLab pipeline can call upon successful deployment. Add a job to your .gitlab-ci.yml that runs after your deploy step completes successfully.
This job tells QA Wolf that a new deployment is ready for testing.

Verify the integration

1

Push a commit

Push a commit to trigger a deployment.
2

Confirm the run appears

Confirm a new run appears in QA Wolf under the expected environment.
Last modified on September 16, 2026