environment keyword — creates a deployment under that environment when it succeeds.
QA Wolf receives those deployments through the connected integration, and a trigger decides which flows run for each one.
Requirements
- Access to a QA Wolf workspace with at least one environment
- Maintainer access to the GitLab group that owns the project
Connect GitLab
1
Create a group access token
The token needs the Maintainer role and the
api scope. QA Wolf refuses anything lower, because a lesser role cannot create the webhooks it reads deployments from.2
Enable the GitLab integration
Paste the token into Workspace settings → Integrations. QA Wolf can then read deployments, set commit statuses, and link runs to GitLab commits.
Give your deployment job an environment
A deployment job needs nothing beyond theenvironment keyword: GitLab creates the deployment itself, and the webhook fires when the job succeeds. Report deployments to QA Wolf has the job.
Two facts decide whether a deployment lands where your triggers look:
- The environment name — QA Wolf matches it against the workspace’s environments by alias or by slugified name, and creates a new environment when nothing matches.
- The
review/prefix — GitLab has no transient flag, so the environment’s name is what marks it short-lived. An environment named underreview/is a review app; anything else accumulates permanently.
url becomes the deployment’s deploy target, which is the address QA Wolf runs against.
A GitLab deployment carries no slot for per-deploy environment variables, so runs against it use the QA Wolf environment’s own variables. To vary them per deploy, report the deploy through the Webhook path instead.
Test every merge request
A review app gives QA Wolf a deployment that resolves to the merge request it came from, which is what makes merge-request testing possible. Two things have to hold, both covered in Report deployments to QA Wolf: the environment’s name is unique to the merge request, and so is itsurl.
Give review apps their own trigger rather than widening the one that covers staging. Match the shape your pipeline emits — review/* — and choose what runs:
- A small tag, for a fixed set of fast flows on every merge request.
- Generative flow selection, which lets QA Wolf pick the flows from the merge request itself. It needs the deployment to resolve to a merge request, so it fits a review-app trigger and skips any deployment without one.