Automated testing in GitLab CI on every merge request
QAShift generates Playwright tests for your product and runs them as a GitLab CI job on each merge request, so broken journeys are caught before they merge.
GitLab pipelines make it easy to run anything on every merge request. The difficulty is having tests worth running: end-to-end coverage that reflects real journeys and stays reliable as the product changes.
QAShift commits tests to your GitLab repository as ordinary Playwright code and adds a pipeline job that runs them, with artifacts for every failure.
How it works with GitLab CI
- 1
Connect GitLab
Grant scoped access to the projects you want tested.
- 2
Generate tests
QAShift writes tests for your journeys and APIs and opens a merge request.
- 3
Add the CI job
A job in .gitlab-ci.yml runs the suite on merge requests and the default branch.
- 4
Act on results
Pipeline status, artifacts and summaries show exactly what broke.
What you get
- Merge request pipeline status
- Video, trace and screenshots as job artifacts
- Works with shared or self-hosted runners
- Unlimited runs
Frequently asked questions
Are runs in GitLab CI limited?
No. Tests run on your own GitLab CI runners, so runs are unlimited on every QAShift plan, including Free.
Do the tests need a special runner or plugin?
No. Tests are standard Playwright, so they run with the usual Node and Playwright setup used by any project.
Can failures block a merge?
Yes. The test job reports a status check, and on paid plans flaky failures are classified so only verified failures block.
Ship without fear.
Start testing free in minutes, or let a QAShift engineer deliver your first morning report within 5 days.