Skip to main content
Free plan, no cardStart free
Topic · updated 2026-11-04

CI/CD testing: pipelines, exported tests and security gates

Testing in CI/CD means a change cannot reach production without the checks running against it: unit and API tests on every push, a browser smoke test on every deploy, the fuller regression suite and security scans where they fit the budget. The hard part is not running tests in a pipeline; it is keeping the pipeline fast and its failures believable.

The pages here say per provider how to run exported tests, how to run only what a change touched, and where security checks belong. They also say, per integration, what is not wired today: there is no trigger that starts a platform run from your CI, and the pages do not pretend otherwise.

What people search for

The literal queries this hub is written to answer; each leads to one of the pages below.

  • ci cd testing
  • github actions playwright tests
  • test automation in jenkins
  • gitlab ci test automation
  • security testing in ci/cd
  • qa automation for ci/cd

Do it: per provider

Each page states what runs and what does not.

Learn: what belongs where

Strategy articles with measured numbers.

Prove it

Alerts, exports and the tools.

Questions people ask

Can my CI pipeline trigger a Dokimore run?

Not today. Tests exported from a recording run in any CI as Playwright, Selenium, Robot Framework or pytest files; a platform run is started from the app or on a schedule, and monitor alerts reach Slack, Teams, PagerDuty, Opsgenie or a signed webhook. Each integration page states exactly this so nobody plans around a trigger that does not exist.

Which tests should run on every pull request?

The ones that answer within the budget the team will wait for: unit and API tests, and the browser scenarios a change touches. Smart test selection picks those with a written reason per pick. The full regression suite and security scans run on a schedule or before a release, where their minutes are not on the critical path.

Should security scans run in CI?

Fast, deterministic checks yes: dependency and secret scanning, and API tests that assert security headers. A DAST scan of a running application is slower and needs a target you are authorised to scan, so it belongs on a schedule or a staging deploy. The security-in-CI/CD article draws the line with numbers.

Try it on your own application

The Free plan asks for no card and runs for 14 days after the trial: record a flow, replay it, and read the evidence each step produced.

Try it against your own app.

Record one flow and get four kinds of evidence back. Judge the results yourself.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India