Skip to main content
The GitLab integration connects your repositories to TestDino for automated test reporting. Test summaries post directly to merge requests and commits.

​
How It Works

TestDino detects Playwright runs from GitLab CI and attaches results to the corresponding merge request or commit.
  • Posts AI-generated test summaries as comments on merge requests and commits
  • Each comment includes a link back to the full TestDino run
  • Branch mapping controls where comments appear
  • Merge request sync keeps TestDino in sync with MR state (open, merged, closed)
Only one Git provider (GitHub or GitLab) can be active per project at a time.

​
Quick Start Steps

1

Connect GitLab

Go to Project Settings → Integrations → CI/CD and select GitLab. Authorize TestDino to access your GitLab account and select the repository.
2

Configure comments

Click the settings icon on the GitLab card to open Comment Settings. Map branch patterns per environment and toggle comments for merge requests and commits.
Branch mapping must be configured before enabling comments. Environment overrides take precedence over global defaults.
3

Run CI

Push code or open a merge request. Your Playwright pipeline triggers as usual.TestDino receives test results and posts a summary comment to the merge request or commit.

​
Merge Requests in TestDino

The Pull Requests page displays GitLab merge requests alongside test results. Each row shows the MR title, author, state, latest test run, and pass/fail/flaky/skipped counts. Click any merge request to open the detail view with Overview, Timeline, and Files Changed tabs.

​
CLI Compatibility

The GitLab integration works with the current and previous versions of the TestDino CLI. No changes to npx tdpw test or playwright.config.ts reporter configuration are needed.

GitHub Integration

Connect GitHub repositories to TestDino

Pull Requests

View merge requests with test results

Environment Mapping

Map branches to environments

Node.js CLI

Install and configure the TestDino CLI