GitHub Actions: your exported tests in a workflow you own
Dokimore has no GitHub Action, command-line tool or CI token today. What works is the exit path: copy a recording as a @playwright/test spec, commit it, and let a workflow you own run it on every push, failing the job when a test fails.
Which way the data flows
Dokimore to your repository, by copy. Nothing calls Dokimore from GitHub, and no result flows back to it.
Set it up
- Open a recording, choose Export, pick Playwright (TypeScript) and paste the copied spec into your repository, for example tests/checkout.spec.ts.
- Add @playwright/test as a dev dependency so npm ci installs it on the runner.
- Create .github/workflows/e2e.yml with actions/checkout, actions/setup-node, npm ci, npx playwright install --with-deps and npx playwright test.
- Upload the playwright-report folder with actions/upload-artifact so a failed run keeps its HTML report, and pin third-party actions to a commit SHA, as GitHub advises.
Where it stops
Stated plainly
- Not available yet: a Dokimore GitHub Action, a scoped CI token, quality gates evaluated by Dokimore, or run results sent back to it.
- An exported spec carries the locators current at export time. It does not self-heal, so export again after you re-record a step whose locator changed.
Questions buyers ask
Does the workflow fail when a test fails?
Yes, because npx playwright test exits with a non-zero code when a test fails. That is Playwright’s own behaviour, not a Dokimore gate.
Can Dokimore start the workflow or read its result?
Not today. Your workflow is the whole integration: it runs the exported tests and keeps their results in GitHub.
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.tsx
Related pages
- CI/CD integration guide
- Test recorder and self-healing
- Every integration, by job
- GitHub Actions: GitHub Actions documentation (the vendor’s documentation, read 2026-11-10)
Also under CI/CD: GitLab CI · 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.