Any CI system: no signed webhook trigger yet, and what works instead
A CI system cannot start a Dokimore run today: there is no webhook trigger, no command-line runner to install and no CI token. Exported code is the path that works, in any system that can run Node or Python.
Which way the data flows
Dokimore to your repository by copy. Nothing travels from your CI to Dokimore.
Set it up
- Export the recording as Playwright (TypeScript or Python), Selenium (Python) or Robot Framework, whichever your CI image already has.
- Commit the code and its dependency file, and add one job that installs the dependencies and runs the suite after your deploy step.
- Write JUnit XML with the framework’s reporter so CircleCI, Buildkite or TeamCity can show the failures.
Where it stops
Stated plainly
- Not available yet: a signed webhook that starts a Dokimore run, a Dokimore CLI with exit codes, a scoped CI token, or a run-completion webhook.
- API collections cannot be run from CI either: the collection runner is used from the browser, where you are signed in.
Questions buyers ask
Why does this page say what does not exist?
Because a team that wires a trigger into its pipeline and sees nothing run has been misled. If a trigger ships, this page will describe it and name the file that implements it.
Which exit code does an exported suite return?
The framework’s own: Playwright Test and pytest exit non-zero when a test fails, and Robot Framework exits with the number of failed tests.
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.ts
Related pages
Also under CI/CD: GitHub Actions · GitLab CI · Jenkins · Azure DevOps · Bitbucket Pipelines
Try it against your own pipeline
Free plan, no card; the integrations on this page are on every plan.