What BitAssure is

BitAssure checks that your website, Android app, iPhone app or API still does what it should. You walk through it once in a real browser or phone, and on each screen you say what should be true: the total reads $64.97, the Pay button is enabled, the welcome message is visible. BitAssure then walks the same path again whenever you ask, on a schedule, or from your CI pipeline, and tells you in your own words which of those things stopped being true.

There is no test code to write. A run gives you a pass or fail for every check, a video with each check marked at the moment it was judged, a PDF report anyone can read, and JUnit XML for your pipeline.

The words BitAssure uses

Word	What it means
Project	One product of yours, such as "Storefront" or "Retail Bank".
Platform	One place that product runs: its website, its Android app, its iPhone app or its API. A project has at most one of each. Older screens call this a target.
Journey	One flow through a platform that you record in one go, such as "Sign in" or "Send money". On an API it is called a flow.
Scenario	One stop along a journey: the screen you reached and what should be true on it. A journey is a series of scenarios.
Step	One thing done on the way: a click, typing into a field, a scroll. Steps are recorded, never written by hand.
Check	One thing that should be true, said about one element: "Confirm is enabled". A check either holds or it does not.
Run	One walk through a journey (or every journey on a platform) with every check judged. A run ends as passed, failed or error.
Credit	What everything is paid in. A website or API run is 1 credit. A phone is charged by the minute.

How it fits together

Project: Storefront
├── Platform: Website (https://shop.example.com)
│   ├── Journey: Sign in
│   │   └── Scenario: Verify Accounts      ← checks: "Balance is visible", …
│   └── Journey: Checkout                    (starts where Sign in ends)
│       ├── Scenario: Verify Basket
│       └── Scenario: Verify Payment
└── Platform: Android app (shop.apk)
    └── Journey: Sign in

A journey can start where another one ends. Record "Sign in" once, and "Checkout" begins already signed in, without you recording the sign-in again.

Where to start

• Your first journey takes you from signing up to a first passing run.
• Recording a journey and Checks cover the recorder in full.
• Running from CI and The REST API are for automating runs.

For AI assistants

BitAssure has an MCP server, so Claude Code, Cursor and other assistants can record, write and run journeys for you: see AI assistants (MCP). Every page here is also plain Markdown at /docs/<page>.md, an index is at /llms.txt, and every page at once is at /llms-full.txt.