# TestSnag Docs

> TestSnag runs automated web, mobile, API and SEO tests against your site on a schedule or on demand, and tells you when a journey breaks.

About the product and the company behind it: https://testsnag.com/about

Every article below is plain Markdown. Add `.md` to any docs URL to get the Markdown version of that page. The whole guide in one file: https://testsnag.com/llms-full.txt

## Getting started

What Testsnag is, the vocabulary, and your first test end to end.

- [What Testsnag is, and the words it uses](https://testsnag.com/docs/getting-started/what-is-testsnag.md): The core vocabulary: test, step, assertion, run, suite, and block. Worth five minutes before anything else.
- [Your first test, end to end](https://testsnag.com/docs/getting-started/your-first-test.md): Record a journey, assert the outcome, run it, and read the result. About ten minutes.
- [The Dashboard](https://testsnag.com/docs/getting-started/dashboard-tour.md): Your single screen for the question "is everything okay?", combining KPIs, test health, and recent runs.
- [Getting started checklist](https://testsnag.com/docs/getting-started/onboarding-checklist.md): The one-screen welcome, the checklist that follows you around, and how to hide it or bring it back.

## Building tests

Recording, steps, selectors, assertions, and the AI chat panel.

- [Creating a test](https://testsnag.com/docs/building-tests/creating-a-test.md): Tests are the foundation of Testsnag, and each one is a journey or check you want to keep verifying.
- [Recording with the Cloud Recorder](https://testsnag.com/docs/building-tests/cloud-recorder.md): The fastest way to author a web test is to record live in a remote browser session with nothing to install.
- [Recording with the Browser Extension](https://testsnag.com/docs/building-tests/browser-extension.md): Record from your own Chrome browser when the cloud session cannot reach what you need to test.
- [Steps and selectors](https://testsnag.com/docs/building-tests/steps-and-selectors.md): What each step type does, how elements are targeted, and why some selectors survive redesigns while others do not.
- [Writing assertions](https://testsnag.com/docs/building-tests/assertions.md): Assertions are what turn a recorded click-through into a test that can actually fail.
- [The AI chat panel and Human in the Loop](https://testsnag.com/docs/building-tests/ai-chat-panel.md): Describe a step in plain English, or take the wheel yourself when a flow is easier to demonstrate than describe.
- [Test settings](https://testsnag.com/docs/building-tests/test-settings.md): One page holds scheduling, notifications, integrations, reports, triggers, and sharing for a single test.
- [Generating a test from a requirements document](https://testsnag.com/docs/building-tests/prd-import.md): Paste the spec for a feature and let Testsnag draft the steps, instead of starting from a blank recorder.
- [Sharing and importing tests](https://testsnag.com/docs/building-tests/importing-and-sharing.md): Hand a test to a teammate or another account with a single shareable import URL.

## Test types

Web, mobile, API, and SEO tests, and when to reach for each.

- [Web tests](https://testsnag.com/docs/test-types/web-tests.md): The default test type: a real browser walking a real journey through your site.
- [iOS and Android app tests](https://testsnag.com/docs/test-types/mobile-tests.md): Upload a build, drive it on a cloud device in your browser, and replay every tap on each release.
- [API tests](https://testsnag.com/docs/test-types/api-tests.md): Verify backend endpoints directly without a browser, which is faster, less flaky, and ideal for contracts.
- [SEO tests](https://testsnag.com/docs/test-types/seo-tests.md): Audit pages against a configurable set of SEO and content checks on a recurring schedule.

## Reusable building blocks

Blocks, scripts, variables, environments, saved requests, and files shared across your tests.

- [Blocks](https://testsnag.com/docs/building-blocks/blocks.md): Save a group of steps once, reuse it across every test that needs it, and fix it in one place.
- [Scripts](https://testsnag.com/docs/building-blocks/scripts.md): Drop into Node, Python, or TypeScript for the steps that clicking cannot express.
- [Variables, test-level and global](https://testsnag.com/docs/building-blocks/variables.md): Keep credentials, environment URLs, and generated values out of your steps and in one editable place.
- [Environments](https://testsnag.com/docs/building-blocks/environments.md): Run the same test against staging, production, or any other copy of your site, each with its own base URL and variables.
- [The saved request library](https://testsnag.com/docs/building-blocks/api-requests.md): Save an HTTP request once and reuse it across API tests, instead of retyping the same call.
- [Files](https://testsnag.com/docs/building-blocks/files.md): Store assets your tests reference at runtime, including file uploads, fixtures, and sample documents.

## Running tests

Runs, results, schedules, suites, triggers, and analytics.

- [Running a test](https://testsnag.com/docs/running-tests/running-a-test.md): Replay every recorded step against your live site and watch the result happen in real time.
- [Reading run results](https://testsnag.com/docs/running-tests/reading-run-results.md): The Runs page is where every execution lives, and where you diagnose what went wrong.
- [Run recordings and sharing them](https://testsnag.com/docs/running-tests/recordings.md): Watch what the browser actually did, and hand somebody a link to it without giving them an account.
- [The Runs list and history](https://testsnag.com/docs/running-tests/runs-and-history.md): Every execution across the workspace in one place, and what the history is actually good for.
- [Scheduling tests](https://testsnag.com/docs/running-tests/scheduling.md): Turn a test into an always-on monitor by running it automatically on a recurring schedule.
- [Suites](https://testsnag.com/docs/running-tests/suites.md): Group related tests so they run, schedule, and notify together as a single unit.
- [Triggering tests with webhooks](https://testsnag.com/docs/running-tests/webhook-triggers.md): Run a test from anywhere, including CI pipelines, deploy scripts, and dashboards, by hitting its trigger URL.
- [The command line tool (CLI)](https://testsnag.com/docs/running-tests/cli.md): Ship a new mobile build, point your tests at it, and run them, without opening the dashboard.
- [AI clients (MCP)](https://testsnag.com/docs/running-tests/ai-clients-mcp.md): Connect Claude Code, Codex, Cursor or VS Code to your workspace so an AI assistant can build, run and debug your tests.
- [Claude and ChatGPT](https://testsnag.com/docs/running-tests/claude-and-chatgpt.md): Add Testsnag to Claude.ai or ChatGPT and ask about your tests, start runs and debug failures from a chat.
- [Analytics](https://testsnag.com/docs/running-tests/analytics.md): Pass rate over time, and which tests are slowest, flakiest, and busiest.

## Notifications and integrations

Slack, email, webhooks, issue trackers, and spec imports.

- [Notifications and integrations](https://testsnag.com/docs/notifications/notification-settings.md): Connect Slack, GitHub, and email so tests speak up where your team already lives.
- [Email reports](https://testsnag.com/docs/notifications/email-reports.md): Get a scheduled summary of how a test or suite is doing, sent daily, weekly, or monthly.
- [The test inbox](https://testsnag.com/docs/notifications/email-inbox.md): A real mailbox your tests can receive at, so sign-up confirmations and one-time codes can be part of the journey.
- [Outbound webhooks](https://testsnag.com/docs/notifications/outbound-webhooks.md): Have Testsnag POST to your own service whenever a run finishes, signed so you can trust it.
- [Running tests from GitHub](https://testsnag.com/docs/notifications/github-actions.md): Run tests and suites on every deployment, post results to the commit, and block pull requests when preview tests fail.
- [Issue trackers: Trello, Jira, GitHub Issues, and Linear](https://testsnag.com/docs/notifications/issue-trackers.md): Turn a failing run into a ticket on the board your team already works from.
- [Importing from Postman, OpenAPI, and GraphQL](https://testsnag.com/docs/notifications/api-spec-imports.md): Build API tests from the specification you already maintain instead of retyping every endpoint.

## Workspace and account

Workspaces, roles, account settings, billing, and what each plan unlocks.

- [Workspaces, roles, and invitations](https://testsnag.com/docs/workspace/teams-and-roles.md): How work is separated between workspaces, who can do what, and how to bring people in.
- [Account settings](https://testsnag.com/docs/workspace/account-settings.md): Update your profile, change your password, and switch between light and dark themes.
- [Billing and plans](https://testsnag.com/docs/workspace/billing-and-plans.md): See your usage, change tier, and manage your subscription from one page.
- [What each plan unlocks](https://testsnag.com/docs/workspace/plan-comparison.md): The limits and features that change between plans, and which ones actually matter as you grow.

## Troubleshooting

Flaky tests, broken selectors, logins, timeouts, and credits.

- [A test that passes and fails at random](https://testsnag.com/docs/troubleshooting/flaky-tests.md): Flakiness is a timing problem far more often than it is a real bug. Here is how to find which.
- [A test broke after a UI change](https://testsnag.com/docs/troubleshooting/broken-selectors.md): When a redesign lands, the steps that fail are usually pointing at elements that no longer exist.
- [Testing pages that need a login](https://testsnag.com/docs/troubleshooting/tests-behind-login.md): The cloud runner starts with no cookies and no session. Every run has to log in for itself.
- [Timeouts and slow pages](https://testsnag.com/docs/troubleshooting/timeouts.md): What a timeout actually means, and why raising the limit is usually the wrong response.
- [Run failed, or your site failed?](https://testsnag.com/docs/troubleshooting/run-vs-test-failure.md): Not every red run means your product is broken. Telling the two apart is the first step of any investigation.
- [Out of runs for the month](https://testsnag.com/docs/troubleshooting/out-of-credits.md): What happens when the allowance runs out, and how to make it last longer.
