1
Create an account
Sign up at app.testorim.com. Testorim asks you
to pick a plan and add a card before the first run. Current plans and
trial terms are on the pricing page.
2
Point it at your site
On the dashboard, type the address of the app you want to test (just the
host and path,
https:// is already there) and press Start.That creates a project for the address and drops you into its chat. A
project is the unit everything else hangs off: runs, saved tests,
environments, schedules and integrations all belong to one.3
Describe a test
Type what you want checked, in a sentence:Press send. If the test needs a value Testorim cannot invent, such as a real
account’s email and password, it stops and asks for it in a form
rather than making one up.
4
Watch it run
The browser panel streams screenshots as the run progresses; the execution
bar shows each step turning from pending to running to passed or failed.On a narrow screen, the chat, browser, reports and saved-tests panels
become a tab strip, one at a time.
5
Read the report
When the run finishes, the report panel fills in: a pass/fail header with
the step counts, a walkthrough of what happened, and, where a step failed,
the element’s real state and a screenshot from the moment it failed.Every run also has its own page at
/runs/<run-id> with the full evidence:
per-step snapshots, console messages, network requests, accessibility
findings and performance metrics.6
Save it so it can run again
Press Save as test on a run you are happy with. That stores the steps
as a procedure, which replays exactly as recorded: no planning, no
model call, no drift.Procedures are what you schedule, what CI triggers, and what the GitHub PR
bot runs.
Where to go from here
Write tests that hold up
The habits that make a test pass for the right reason.
Environments
Run the same test against staging and a PR preview.
Run from CI
Install the CLI and trigger a procedure from a pipeline.
Alerts
Get told in Slack or email when a scheduled run fails.