Skip to main content
A project represents one website under test. Everything else in Testorim belongs to a project: its runs, its saved tests, its environments, its variables, its schedule, its Slack channel, its GitHub repository.

​
Creating one

On the dashboard, type the site’s address into the address bar and press Start.
  • https:// is already supplied, so type shop.example.com, not the scheme.
  • If a project already exists for that address, you are taken to it rather than getting a duplicate.
  • You land in the project’s chat, ready to describe the first test.
The address you give becomes the project’s base address. Every run starts there, and a step that navigates to a relative path (/checkout) resolves against it.
Private and internal addresses are refused: localhost, loopback, RFC1918 ranges, link-local and cloud metadata endpoints. The guard applies twice: once when you save the address, and again to every request the page makes during a run. Expose a local build through a tunnel and use the public URL.

​
The project overview

/project/<project-id> is the project’s home, showing:
  • Stats: runs in the last 30 days, pass rate, number of saved tests, last run
  • Recent runs: with their status, jumping to the full run page
  • Saved tests: with replay counts and a Run button
  • Flakiness: pass rate per test over a rolling window, worst first
  • Recent PR activity: when a GitHub repository is linked
  • Integration chips: a row under the address showing what is wired up: repository, Slack channel, email recipients, schedules, environments, variables, login reuse. Each one jumps to the setting it names.
The chat lives at /project/<project-id>/chat and the settings at /project/<project-id>/settings.

​
Settings

Project settings has one section per capability, each linked from the integration chips:

​
Reusing a login

If you save a sign-in flow as a procedure and mark it as the project’s login-setup test, a successful run captures the browser’s storage state and encrypts it onto the project. Later runs start already signed in and skip the login flow. See Reusable flows.

​
Archiving

Deleting a project archives it. The project disappears from the dashboard, but its historical runs are retained. A passing run from three weeks ago stays readable, and its share links keep working.

​
Who can do what

Projects belong to a workspace, and every query is scoped to it. A project in one workspace is invisible from another, and asking for it by id returns not found rather than forbidden. Nobody can grant, change or remove a role above their own, and the last owner can never be demoted or removed.