Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.testsprite.com/llms.txt

Use this file to discover all available pages before exploring further.

This page is the conceptual map of what a first run feels like. It’s the same shape for UI and API projects: configure → understand your product → explore or discover → plan → generate → run → review. For the click-by-click version, jump straight into the type-specific walkthrough that matches the project you’re starting with.

UI Quickstart

Walk through your first frontend project end-to-end (~10 min)

API Quickstart

Walk through your first backend project end-to-end (~10 min)

​
The Lifecycle

1

Project Setup & PRD Upload

Name the project and upload your PRD (or any product-spec document). PRD upload is strongly recommended — it’s the single biggest lever on plan quality. Skip it only for a quick demo.
2

Feature & Use-Case Extraction

TestSprite reads your PRD and produces a feature map — a structured list of features and the use cases under each, rendered as a flow graph. This is what grounds the rest of the run. Skipped if no PRD was uploaded.
Use Cases & Features flow graph
3

Configuration

Provide your live URL and credentials. UI projects ask for a starting URL + test account; API projects ask for the base URL + auth type + your API documentation.
Configuration form
4

Exploration or Discovery

For UI projects, TestSprite walks your live app feature by feature, targeting the use cases from the feature map. For API projects, TestSprite reads your docs and confirms endpoint shapes against the live URL.
Feature exploration in progress
5

Plan Review

A test plan is drafted from what was observed. You review, edit descriptions in natural language, deselect cases you don’t want, then click Generate Tests.
Plan review
6

Test Generation

TestSprite converts the approved plan into Python tests (with Playwright for UI), verifies each one in our cloud sandbox, and surfaces failed verifications clearly.
7

Execution

Tests run in the cloud and stream results back. Each row surfaces one of: Pending, Running, Pass, Failed, Blocked.
Tests executing
8

Review and Refine

The Test Report tab summarizes pass/fail counts, highlights failures with cause-and-fix suggestions, and links into per-test detail. To iterate on a specific test, open it and use the Chat tab — describe what to fix in natural language.
Test report

​
Where to Go Next

UI Quickstart

Click-by-click walkthrough for frontend projects

API Quickstart

Click-by-click walkthrough for backend projects

Key Terms

Vocabulary used across the rest of the docs

Testing Lifecycle

The lifecycle in more detail, with UI vs API differences called out