GitLab Merge Request Reviews and CI/CD

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. GitLab sign-in is only needed for path B. Path A authenticates with a QA.tech API key.

• 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
• Environment basic auth - Persist domain-scoped HTTP basic auth from the Start Run API
• PR Testing for Mobile Apps - Upload MR binaries and pin change reviews with applicationBuildShortId