Testing Lifecycle - TestSprite Documentation

Every project moves through the same phases, and either way the plan is grounded in how your product actually behaves: UI projects explore your live app, and API projects discover endpoints from your docs and probe them against your live API.

The Phases

Phase	What happens	Learn more
Setup	Create the project with `New Project`, set how TestSprite signs in, and add sources: your PRD (strongly recommended), and for API projects your API docs	Project Sources
Explore / Discover	UI: agents walk your live app. API: TestSprite reads your endpoints from the docs and probes them against your live API	Feature Exploration, API Discovery
Feature map	Features and use cases, shown on `Test Coverage`, where you can edit them	Coverage Map
Plan	After you click `Plan Tests`, the testing agent plans test cases scoped to the feature map. You keep, edit, or remove them	UI, API
Run	Tests are generated and run in the cloud. API tests pass captured values to the tests that depend on them	Dependency Chains
Review	A verdict per test, with recordings (UI) or requests and responses (API), and a suggested cause and fix for failures	Test Detail Page
Notify	Post run summaries to Slack and turn failures into tickets	Slack, Ticketing
Iterate	Edit a test’s description, ask in `Chats`, or re-run a single test to confirm a fix	Managing Test Cases

UI vs API: What’s Different

Phase	UI Testing	API Testing
Exploration	Agents walk your live app, page by page	TestSprite calls your endpoints and records the real responses (Probe response and Raw call records on `Test Coverage`)
Plan grounding	Real screens and copy observed during exploration	Your API docs and instructions, plus the responses observed from your live API
Execution artifacts	Video recordings, step-by-step screenshots, console output	HTTP requests/responses, status codes, response bodies
Authentication	Sign-in to your app: test account credentials, OTP (one-time password) login, or SSO (single sign-on) such as Google	Credentials on the requests: a token, API key, or a refresh grant TestSprite renews before each run
Failure analysis	AI cause-and-fix with screenshot of the failing step	AI cause-and-fix with the offending request/response diff
Cleanup	Not applicable, no persistent resources created	Automatic post-run sweep of created records, files, and sessions

Where to Go Next

UI Quickstart

The UI flow, click by click

API Quickstart

The API flow, click by click