Skip to main content

Quick start: your first recorded test in one sitting

Create a free account, verify your email, name a workspace, point the recorder at a URL you are allowed to test, and click through one flow. The recording replays as a regression test straight away. Nothing is installed on your machine.

Before you start

You need a work email and a web application you are permitted to test. The Free plan does not ask for a card. It includes 100 recordings, 1,000 API test calls and 10 security scans per month for one user, which is enough to evaluate every module in this guide.

Steps

  1. Open Sign up and enter your name, work email and a password. If your company domain has SSO configured, you are offered it here.
  2. Verify your email from the message we send. The link returns you to the app.
  3. Create a workspace. On the Team plan this is where you will invite up to 15 members later; on Free and Solo Pro it is just yours.
  4. Open the Test Recorder and enter the URL of the application under test. The crawler maps the pages it can reach and catalogues the elements on each one.
  5. Start a recording and click through one journey in the real browser that opens, for example sign in, add an item, check out. Every step, selector, network call and assertion is captured as you go.
  6. Stop the recording and run it. The first replay is your regression baseline. From the same recording you can start a load profile, a security scan and an accessibility audit.

What you have after the first run

Each recording produces seven structured files: session metadata, element details, network data, performance data, security data, UI elements and a rerun definition. Element and request IDs are stable, so a security finding can point at request req_0012 and the replay can point at element elem_0004 without copying either. You can export the recorded flow as Playwright, Cypress or Selenium code at any time.

Where people get stuck

  • The application needs a login: record the sign-in steps as part of the flow, or store the session once and reuse it. Auth state persists between recording and replay.
  • The page uses a shadow DOM or iframes: recording works, but check the captured selectors on the first replay and approve any heal the review queue proposes.
  • You want to test a site you do not own: the security scanner will refuse until ownership is proven. See the security guide for how ownership is verified.

Questions people ask about this

Do I need to install anything?
No. Recording, replay and every scan run in the platform. Exported Playwright, Cypress or Selenium code runs wherever you normally run those frameworks.
Does the free plan expire?
No. The Free plan has monthly caps, not a time limit. Paid plans include a 14-day trial (30 days on Enterprise) and can be cancelled at any time.

Source: /documentation/quick-start, updated 2026-09-16. Answers are checked against the shipped product on that date.

Found something out of date? The people who build the module answer the contact form on the home page, and corrections to this guide are dated above. Tell us.

Getting started

Platform overview: sixteen modules, one set of test assets

Dokimore is one workspace in which UI recording, API testing, load testing, security scanning and accessibility auditing read the same envir…

8 min
Recording and self-healing

Recording your first test

The recorder opens a real browser, you click through a journey, and it captures each step with the element it targeted, the locators availab…

6 min
Security and data handling

Security and data handling

Cloud tenants are hosted in Mumbai, India. Connections are encrypted with TLS, stored credentials are encrypted at rest, sign-in supports pa…

8 min

Your choice about analytics

We use one optional analytics tool, run on our own servers, to see which pages help people. It stays off unless you turn it on. Storage needed to sign you in, keep the site secure and remember this choice is always on. Cookie Policy