GitLab CI: exported tests in your own pipeline, on gitlab.com or your own server
There is no Dokimore runner, token or pipeline template for GitLab today. A recording copied as a @playwright/test spec runs in any GitLab pipeline, and Playwright’s JUnit reporter feeds GitLab’s own test report.
Which way the data flows
Dokimore to your repository by copy. The pipeline runs on your runners and reports in GitLab only.
Set it up
- Copy the recording as Playwright (TypeScript) from the Export menu and commit it with a package.json that lists @playwright/test.
- In .gitlab-ci.yml, run the job in the mcr.microsoft.com/playwright image whose tag matches your @playwright/test version.
- In the script, run npm ci, then npx playwright test --reporter=junit with PLAYWRIGHT_JUNIT_OUTPUT_NAME set to results.xml.
- Declare artifacts:reports:junit with results.xml so the merge request lists the tests that failed.
Where it stops
Stated plainly
- Not available yet: Dokimore triggering a GitLab pipeline, reading its jobs or logs, or issuing a token for GitLab CI/CD variables.
- Runner capacity is yours: a heavy browser suite on a shared runner is bounded by that runner.
Questions buyers ask
Does this work on a self-managed GitLab?
Yes. Nothing talks to Dokimore, so any GitLab that can pull the Playwright image and run npm can run the exported spec.
Can I export Python instead of TypeScript?
Yes. Playwright (Python), Selenium (Python) and Robot Framework exports run in a Python image with pytest or robot; the job layout stays the same.
Where it is implemented
The files in our code that carry this integration. A catalogue test checks that each still exists, so this page cannot outlive the feature.
backend/src/modules/recordings/services/framework-code-emitter.tsbackend/src/modules/recordings/services/playwright-ts-code-export.tsfrontend/src/modules/recordings/components/ExportCodeMenu.tsxbackend/src/modules/qa-testing/services/export/robot-framework-export.ts
Related pages
- CI/CD integration guide
- Test recorder and self-healing
- Every integration, by job
- GitLab CI/CD: GitLab CI/CD documentation (the vendor’s documentation, read 2026-11-10)
Also under CI/CD: GitHub Actions · Jenkins · Azure DevOps · Bitbucket Pipelines · Any CI system
Try it against your own pipeline
Free plan, no card; the integrations on this page are on every plan.