Skip to main content
UI testing overview
UI Testing takes you from “here’s my web app” to a regression suite that catches UI bugs without breaking on every minor refactor.

​
Key Features

​
The UI Testing Journey

Each step has its own page. New to TestSprite? Start with the Quickstart, which walks the whole journey in about 10 minutes.

Authentication (UI)

Configure how TestSprite signs in: test account credentials, OTP, or SSO

Feature Exploration

How TestSprite walks your live app to discover what to test

Plan Generation & Editing

Review the plan grounded in observed flows; edit, add, prune

Test Generation & Execution

Python + Playwright code per test case

Step-by-Step Replay

Per-step screenshots, video, and behavior trace for one test

Agent Actions

Every recording from a run, bucketed by status

Edit & Rerun

Re-execute a single test, the whole project, or a scheduled run

Auto-Heal

Recover UI tests when the page changed but the flow is fine
Each UI test is self-contained: sign in, do the thing, assert. Unlike API tests, no data is passed between tests, so the work is in the single test (the page, timing, and absorbing UI change).

​
Where Things Live

A UI project’s sidebar is grouped into Setup, Workspace, Analytics, Activity, and Project Settings; see the Test Detail Page for what each item does. Scheduling lives outside the project, under Automation → Test Schedules.

​
Refining Tests in Natural Language

You can refine any test in plain language, by editing its description or asking in Chats. For example:
Review proposed tests: edit and refine test cases before confirming
See Managing Test Cases for every way to do it.

​
Testing an API Instead?

See API Testing. The flow mirrors this one; API projects discover and probe endpoints instead of walking pages, chain tests that depend on each other, and use Auto-Auth for token refresh rather than Auto-Heal. Testing Lifecycle compares the two side by side.