1
Create an account and start a trial
Sign up at app.testorim.com. Before anything
else, Testorim asks you to choose a plan (Starter, Pro or Team) and add a
card. Every plan starts with a 3-day trial: 10 runs, 30 browser minutes,
one run at a time, and nothing charged until it ends. See
Plans and limits.
2
Point it at your site
On the home page, type the address of the app you want to test (just the
host and path,
https:// is already there), optionally give the project a
name, and press Start.That creates a project for the address and opens its Test tab, with a
short “Help Testorim understand this app” form you can fill in or close. A
project is the unit everything else hangs off: runs, procedures,
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.
If every test browser is busy, the chat shows your place in line and the
run starts by itself when one frees up.On a narrow screen, a Chat | Browser switch shows one panel at a time.
5
Read the report
When the run finishes, the report appears in the chat: the step counts, a
walkthrough of what happened, and a Result of Passed, Failed or
Needs review. Where a step failed, it shows 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:
every step, console messages, network requests, accessibility findings,
performance metrics and the recording.6
Save it so it can run again
Press Save as procedure under a run you are happy with, and name it.
That stores the steps as a procedure, which replays exactly as
recorded: no planning, 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.