Quickstart

Aback Inspect runs browser tests against your website in Chromium on Cloudflare and shows, step by step, what passed and what broke. This guide walks through your first tests.

1. Run the sample suite

Every new workspace has a Sample: Acme Notes project that tests a small demo app: signing in, a wrong password, creating a note, a visual check and a crawl. On the overview, choose Run the sample suite. Each test opens a real browser; results usually arrive within a minute or two. The sample does not count towards your plan's projects or tests, but its runs do count towards your monthly runs.

2. Add your website

Go to Projects, New project, enter the URL tests should start from (a staging site is best), and confirm that you are allowed to test it. If your pages load scripts, APIs or sign in widgets from other hosts, list them as third party hosts: the browser can only reach hosts you allow. Each run lists any requests it blocked, with a button to allow them.

3. Write a test

Open the project and choose New test. Start from a template such as Smoke test or Sign in, then adjust the steps in the visual builder. Prefer finding elements by role and name or by label: these locators keep working when markup changes. Choose Create and run.

4. Read the result

A failed run shows the failing step, the expected and actual values, the page URL, a screenshot of the page at the moment of failure, the console and the network requests. Fix the site or the test and choose Run again.

5. Automate it

• Connect your coding agent with the MCP server so it can test features as it builds them.
• Run the suite against every preview deployment from CI.
• Add a schedule and get a Slack message when something that passed starts failing.

The API and MCP server live at https://abackinspect.com/api/v1 and https://abackinspect.com/mcp.