Bitbucket Pipelines: exported tests in your own pipeline step
Dokimore does not read Bitbucket pipelines or steps today. An exported test is ordinary Playwright, Selenium or Robot Framework code, so one pipeline step runs it and Bitbucket’s test reporting picks up the JUnit file.
Which way the data flows
Dokimore to your repository by copy; Bitbucket runs it with your build minutes.
Set it up
- Export the recording from the Export menu and commit the code with its dependency file.
- In bitbucket-pipelines.yml, set the image to the Playwright image that matches your framework version.
- In the step script, install dependencies and run the suite so that it writes JUnit XML into a test-results directory.
- Push; Bitbucket’s test reporting reads JUnit XML from a test-results directory and lists failed tests on the pipeline page.
Where it stops
Stated plainly
- Not available yet: Dokimore reading pipelines, steps or logs, or setting repository variables for you.
- Pipeline minutes are Atlassian’s and billed to you; a long browser suite spends them.
Questions buyers ask
Bitbucket Cloud or Data Center?
Either can run the exported code, because nothing calls Dokimore; the steps above use the Bitbucket Cloud file format.
Can one step run Robot Framework instead?
Yes. Use a Python image, install robotframework and robotframework-browser, run rfbrowser init, then robot --xunit test-results/results.xml.
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
- Bitbucket Pipelines: Get started with Bitbucket Pipelines (the vendor’s documentation, read 2026-11-10)
Also under CI/CD: GitHub Actions · GitLab CI · Jenkins · Azure DevOps · Any CI system
Try it against your own pipeline
Free plan, no card; the integrations on this page are on every plan.