GitLab Merge Request Reviews and CI/CD

Set up automated GitLab merge request reviews and API-driven test runs

Pull request testing

Review a merge request.

Regression testing

Run a test plan from GitLab CI.

There are two independent ways to integrate GitLab with QA.tech. Pick the one that matches what you want to do. They use different setup pages and different credentials.

	A) GitLab CI	B) GitLab MR Reviews
What it does	Triggers QA.tech test plans from your CI/CD pipeline	Runs exploratory tests on merge requests and responds to @qa.tech
Setup page	Integrations → GitLab CI	Integrations → GitLab MR Reviews
GitLab Connection (OAuth)?	Not required	Required — so QA.tech can handle webhooks and post on MRs
Credential	QA.tech API key from Organization Settings → API Keys, stored as the GitLab CI/CD variable QA_TECH_API_TOKEN	The GitLab Connection identity (recommended: a dedicated service user)

A GitLab Connection is only needed for path B. Path A authenticates purely with a QA.tech API key and never touches OAuth.

• Path A setup is on GitLab regression testing.
• Path B setup is on Set up GitLab MR reviews.

Related documentation

• GitLab pull request testing - Start merge request reviews, after merge, or for a mobile build
• GitLab regression testing - Run test plans from GitLab CI
• API Reference - Complete API documentation
• Test Plans - Create and organize test plans
• Preview Environments - Dynamic preview testing
• Environment custom headers - Persist auth and protection-bypass headers from the Start Run API
• PR Testing for Mobile Apps - Upload MR binaries and pin change reviews with applicationBuildShortId