QA.tech + GitLab
The GitLab integration brings both testing modes to GitLab-hosted teams: AI merge-request reviews that analyze changes and post results on the MR, and API-driven test-plan triggers from GitLab CI using dotenv artifacts to pass preview URLs between stages. Per-run Slack channel overrides are supported.
What you can do
- Automatic AI reviews on every merge request
- Trigger test plans from GitLab CI stages
- Pass preview URLs between pipeline stages with dotenv artifacts
- Route a specific run's alerts to its own Slack channel
Set it up
Connecting GitLab
- 01
Connect GitLab in QA.tech's Integrations settings and pick the projects to review.
- 02
In GitLab CI, write the deploy URL to a dotenv artifact so later stages can read it.
- 03
Call the test-plan trigger from a pipeline stage, passing that URL as an override.
- 04
We wrote a full GitLab CI/CD walkthrough with the pipeline YAML.
Full reference in the QA.tech docs.
Where teams use this
GitLab in practice
GitLab teams get the same before-merge coverage as the GitHub App: MRs are tested against their preview build, which makes it a natural fit for validating AI-generated code and for shift-left workflows. On the pipeline side it drives smoke checks and critical-path regression plans across staging and preview environments.
FAQ
Common questions
- Is the MR review the same as the GitHub App?
- Functionally yes: change analysis, test creation, execution on the preview build, results on the MR.
- How do preview URLs get to the test run?
- Through dotenv artifacts passed between CI stages, then into the trigger call.
Related integrations
GitHub Actions
Next →CI/CD REST API
Your team moves fast. Can your testing keep up?
QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.