Quickstart
From signing in to reading your first report.
How it works
What happens between your sentence and the report.
Write a good test
What to say, and what not to guess at.
API and CLI
Run tests from CI with an API key.
What it is good at
Workflows, not units. Testorim exercises the paths a customer actually walks: sign-up, sign-in, search, checkout, settings changes, form validation. It drives the rendered page, so it sees what a person sees. Answering a question about a live site. Every run ends with evidence: the screenshot at the moment of failure, the element’s real state read back off the page, the console errors and network calls captured during the step. A report never claims something nobody looked at. Telling your bug from its own. A failed step is attributed before it is narrated: the site misbehaved, the step did not match the page, the request is outside what a browser can observe, or Testorim itself broke. You are not sent to debug a working site.What it is not
Testorim is not a unit-test runner, a load tester, or a replacement for the tests that live next to your code. It does not read your source, and it does not know your app’s internals. It knows the page in front of it. It also cannot observe anything that never reaches the browser: an email that was sent, an SMS that arrived, a row written to a queue, a log line on your server. A test that asks for one of those is marked unsupported rather than quietly passed. (A database assertion is the one exception, and only against a read-only connection you configure yourself.)Where to go next
Core capabilities
The full list of what a run can do.
Create your first test
Write one sentence and watch it run.