> ## 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.

# What is Testorim

> Testorim turns a plain-English description of a workflow into a browser test, runs it in a real browser, and reports what actually happened.

Testorim is browser QA you write in English.

You describe a workflow the way you would describe it to a colleague (*"sign in
with the demo account, add the first product to the cart, and check the cart
badge says 1"*) and Testorim plans the steps, drives a real Chromium browser
through them, and writes up what it observed, with a screenshot behind every
claim.

There is no selector to maintain, no test framework to install, and nothing to
run on your own machine.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/getting-started/quickstart">
    From signing in to reading your first report.
  </Card>

  <Card title="How it works" icon="workflow" href="/introduction/how-it-works">
    What happens between your sentence and the report.
  </Card>

  <Card title="Write a good test" icon="pen-line" href="/test-creation/writing-tests">
    What to say, and what not to guess at.
  </Card>

  <Card title="API and CLI" icon="terminal" href="/developers/platform-overview">
    Run tests from CI with an API key.
  </Card>
</CardGroup>

## 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

<CardGroup cols={2}>
  <Card title="Core capabilities" icon="list-checks" href="/introduction/core-capabilities">
    The full list of what a run can do.
  </Card>

  <Card title="Create your first test" icon="play" href="/getting-started/first-test">
    Write one sentence and watch it run.
  </Card>
</CardGroup>


## Related topics

- [Identify the presented credential](/api-reference/identity/identify-the-presented-credential.md)
- [Steps and expected outcomes](/test-creation/steps-and-outcomes.md)
- [Support](/resources/support.md)
- [Create your first test](/getting-started/first-test.md)
- [GitHub](/integrations/github.md)