Jenkins: exported tests in a declarative pipeline you own
Dokimore does not start Jenkins jobs or read their console output today. An exported test is plain framework code, so a declarative Jenkinsfile runs it like any other suite and the junit step records the result.
Which way the data flows
Dokimore to your repository by copy; Jenkins runs the suite and reports on its own.
Set it up
- Export the recording in the framework your agents already run: Playwright (TypeScript or Python), Selenium (Python) or Robot Framework with the Browser library.
- Commit it with its dependency file, package.json or requirements.txt, next to a Jenkinsfile.
- In the Jenkinsfile, use a Docker agent with the matching image, install the dependencies, and run the suite with a JUnit reporter, for example robot --xunit results.xml.
- Add a post block with always { junit "results.xml" } so a failed test marks the build and the report survives the failure.
Where it stops
Stated plainly
- Not available yet: Dokimore starting a Jenkins job, reading a build, or holding Jenkins credentials for you.
- Robot Framework exits with the number of failed tests, which fails the shell step; publishing the JUnit file in post keeps the report either way.
Questions buyers ask
Is a Jenkins plugin needed?
Only the JUnit plugin most installations already have, for the junit step. Dokimore has no Jenkins plugin.
Where should credentials for the tested site live?
In Jenkins credentials, injected as environment variables. An exported test reads them like any other test, and they never pass through Dokimore.
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/qa-testing/services/export/robot-framework-export.tsfrontend/src/modules/recordings/components/ExportCodeMenu.tsx
Related pages
- CI/CD integration guide
- Test recorder and self-healing
- Every integration, by job
- Jenkins: Jenkins user documentation (the vendor’s documentation, read 2026-11-10)
Also under CI/CD: GitHub Actions · GitLab CI · 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.