GitHub Actions
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.
Set up GitHub ActionsGitLab CI
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.
Set up GitLab CIJenkins
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.
Set up JenkinsAzure DevOps
Dokimore has no Azure DevOps connection for customers today. A recording exported as a @playwright/test spec runs in any Azure pipeline, and the PublishTestResults task shows each test in the run summary.
Set up Azure DevOpsBitbucket Pipelines
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.
Set up Bitbucket PipelinesAny CI system
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.
Set up Any CI system