Overview
The GitLab integration detects Playwright runs from your CI pipeline and posts AI-generated test summaries as comments on merge requests and commits. Each comment includes a link back to the full TestDino run.
Merge request sync keeps TestDino updated with your MR state (open, merged, closed). The Pull Requests page in TestDino displays GitLab merge requests alongside test results, pass/fail/flaky/skipped counts, and timeline views.
Key features
- AI-generated test summaries on merge requests and commits
- Merge request state sync (open, merged, closed)
- Branch mapping with environment overrides
- Pull request page with test results and timeline
- Works with GitLab SaaS and self-hosted
How it works
Connect GitLab
Go to Project Settings, then Integrations, then CI/CD and select GitLab. Authorize TestDino to access your GitLab account and select the repository.
Configure comments
Click the settings icon on the GitLab card to map branch patterns per environment and toggle comments for merge requests and commits.
Run your pipeline
Push code or open a merge request. Your Playwright pipeline triggers as usual. TestDino posts a summary comment automatically.
.gitlab-ci.yml
test:
stage: test
script:
- npx playwright test
after_script:
- npx testdino upload --report-dir playwright-report
artifacts:
paths:
- playwright-report/Branch mapping and environment overrides
Branch mapping must be configured before enabling comments. Map branch patterns to environments so TestDino knows where to post summaries.
Environment overrides take precedence over global defaults. Only one Git provider (GitHub or GitLab) can be active per project at a time.
Note: CI checks that block merges are GitHub-only. GitLab gets MR and commit summaries, but to enforce a merge gate on GitLab, use your pipeline's own job rules to fail the build on a failing test step.