Skip to main content
Free plan, no cardStart free

EVDTest evidence · updated 2026-10-25

Test evidence for every run: linked files, screenshots and proof a reviewer can check

Seven linked files per recorded session, a screenshot and the network calls for each failed step, and proof with every confirmed security finding, limits stated.

For: QA leads and developers who need a failure explained without a rerun, security reviewers who will not accept an unproven finding, and teams that must show an auditor or a customer how a release was tested.

acme-shop / checkout-flow.recIllustrative run
  1. REGRegressionPassed14 / 14 steps · 38.2 s
  2. LOADLoad · 200 virtual usersIn budgetP50 180 · P95 412 · P99 690 ms
  3. SECSecurity · OWASP Top 10 (2025)1 confirmed1 confirmed · 2 observed
  4. A11YAccessibility · WCAG 2.2 A and AA3 issues9 pages · VPAT draft ready
1 selector healed#pay-now-btn[data-test="pay"]Shown in the run

Capabilities

Seven files per recorded session, linked by ID

Element details, network data, performance data, security data, UI elements, session metadata and the replayable rerun definition. Elements, requests and cookies carry stable IDs such as elem_0001, req_0001 and cookie_001, so one file names another’s record instead of copying it, and the format only grows.

Read more: Seven files per recorded session, linked by ID

A failed step that explains itself

The element the step targeted with every locator available for it, the network calls it caused by request ID with their status and timing, the assertion and what was found instead, and a screenshot of the page at that moment: usually enough to tell a changed page from a slow service from a broken test.

Read more: A failed step that explains itself

Every rescue on the record

When a locator breaks and a fallback stored at record time rescues the step, the run shows the locator that failed, the one that matched, the strategy that found it and its confidence, so a person can check that the rescue did not hide a real change.

Read more: Every rescue on the record

Security findings with their proof

A finding is reported as confirmed only with the request that proved it, the response and a proof of concept linked to the recorded request. The evidence bundle carries an integrity badge showing it was not edited after the scan, and each scan records the ownership proof used and who authorised what.

Read more: Security findings with their proof

Accessibility findings and a VPAT draft from the scan

Each finding names the element, the rule, the WCAG criterion and a remediation. The VPAT draft takes its WCAG table from the audit that was actually run; its Section 508 and EN 301 549 tables are left for a person to complete.

Read more: Accessibility findings and a VPAT draft from the scan

Evidence that leaves with you

Each of the seven files downloads on its own from the recording page as JSON, the flow exports as Playwright, Selenium, Robot Framework or pytest code, and security reports export with their evidence attached.

Read more: Evidence that leaves with you

How it works

  1. Record the flow onceClick through the journey in a real browser, on a site you are allowed to test, with a test account and synthetic data. The seven files are produced from that session.
  2. Run it, audit it or scan itReplay the recording as a regression test, audit its pages for accessibility, or scan the site for security once you have proven you own it.
  3. Open the step that failed or was rescuedThe run detail shows the screenshot, the network calls and the assertion, and for a rescued step the locator that broke beside the one that matched.
  4. Take the record outDownload the files you need as JSON from the recording page, export the flow as code, or export the security report with its evidence.
  5. Hand it to the reviewerAttach the files to the ticket, the pull request or the audit request. Every record names the element, request or cookie it refers to by ID, so the reviewer can follow it from one file to the next.

What you receive, and what we do not do

Evidence ledger
Per session
Seven JSON files: element details, network data, performance data, security data, UI elements, session metadata and the rerun definition, linked by stable IDs.
Per failed step
The element and its locators, the network calls by request ID with status and timing, the assertion and what was found, and a screenshot.
Per rescue
The locator that failed, the one that matched, the strategy that found it and its confidence.
Per confirmed security finding
The request, the response, a proof of concept, severity with CVSS, scope and an integrity badge.
Per accessibility finding
The element, the rule, the WCAG criterion and a remediation; manual-review items listed separately.

Limits we state

  • Evidence covers the flows that were recorded and the audits and scans that were run; it does not show that untested paths work.
  • A login typed during a recording is kept, encrypted with AES-256-GCM, so the replay can sign in; passwords are hidden in views, exports and generated code. Record with test accounts and synthetic data.
  • A value the browser did not report is left empty rather than estimated, so some fields are blank by design.
  • There is no CI quality gate yet: a run’s result does not fail a pipeline by itself.
  • The audit log of sign-ins and administrative changes is read by team owners through the API; it has no export and no integrity check yet.
  • Account and recording records are deleted by hand rather than by an automated retention job, including after an account closes.
  • Dokimore holds no SOC 2 report or ISO certificate of its own yet: this evidence supports your audit; it is not an attestation about us.

Plans: The seven files come with every recording, on every plan including Free (10 recordings a month). Security scans start at Solo Pro (on Free, a single Security scanning tool adds 10 a month); accessibility audits are on Solo Pro, Team and Enterprise. See the metering table.

Questions buyers ask

Is a screenshot enough as test evidence?

Rarely on its own. A screenshot shows one moment; a reviewer usually needs what the step did: the element it used, the requests that went out, what came back and the assertion it checked. The FDA’s computer software assurance guidance of February 2026 makes the same point for regulated software, preferring "digital records, such as system logs, audit trails, and other data generated and maintained by the software" to paper documentation and screenshots. A Dokimore run keeps the screenshot and those records together.

Can a run serve as evidence in a SOC 2 or ISO 27001 audit?

As part of it. Change-management controls ask that a change be tested before it ships: a point of focus under the AICPA trust services criterion CC8.1 reads "a process is in place to test system changes prior to implementation", and ISO/IEC 27001:2022 has controls A.8.29 (security testing in development and acceptance) and A.8.32 (change management). A run shows what was tested, when and with what result. It does not record who approved the release, and the auditor decides what is sufficient.

Does it meet FDA or EU AI Act record requirements?

Not on its own, and we do not claim it. The FDA guidance asks for a record of who performed the testing and when; Annex IV of the EU AI Act asks for "test logs and all test reports dated and signed by the responsible persons". A run gives you dated, machine-generated records to attach; the signatures and the quality system around them stay yours.

Can I get the evidence out of Dokimore?

Yes. Each of the seven files downloads from the recording page as JSON, the flow exports as Playwright, Selenium, Robot Framework or pytest code, and security reports export with their evidence attached.

What does the evidence not show?

Paths nobody recorded, values the browser did not report (left empty, never estimated), and whether the page or the test is wrong: a screenshot and a request log explain a failure, and the judgement stays a person’s.

Try it on your own application

The Free plan asks for no card and runs for 14 days after the trial. Or bring one flow from your product and we record it live.

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