> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testorim.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Sign in, point Testorim at your site, and get a report back, in about five minutes.

<Steps>
  <Step title="Create an account">
    Sign up at [app.testorim.com](https://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](https://testorim.com/pricing).
  </Step>

  <Step title="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.

    <Warning>
      The address has to be reachable from the internet. Private and internal
      hosts (`localhost`, `127.0.0.1`, anything in `10.x`, `192.168.x`,
      `172.16-31.x`, link-local) are refused, and so is any request a page
      makes to one mid-run. To test a local build, expose it through a tunnel
      and use the public URL.
    </Warning>
  </Step>

  <Step title="Describe a test">
    Type what you want checked, in a sentence:

    ```text theme={null}
    Open the products page, search for "backpack", and check that at least one
    result mentions Backpack.
    ```

    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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Where to go from here

<CardGroup cols={2}>
  <Card title="Write tests that hold up" icon="pen-line" href="/test-creation/writing-tests">
    The habits that make a test pass for the right reason.
  </Card>

  <Card title="Environments" icon="layers" href="/projects/environments">
    Run the same test against staging and a PR preview.
  </Card>

  <Card title="Run from CI" icon="terminal" href="/developers/cli">
    Install the CLI and trigger a procedure from a pipeline.
  </Card>

  <Card title="Alerts" icon="bell" href="/integrations/overview">
    Get told in Slack or email when a scheduled run fails.
  </Card>
</CardGroup>


## Related topics

- [What is Testorim](/index.md)