What is the TestSprite Web Portal?
The TestSprite Web Portal is a browser dashboard that takes a project from “I have an app” to “I have a passing test suite running on a schedule”, without writing a single line of test code. It complements the TestSprite CLI and the MCP Server, which bring TestSprite into your terminal, IDE, and coding agent, by giving QA, engineering teams, and anyone who’d rather not work from a terminal or IDE a shared place to configure projects, manage credentials, run tests, and review reports.
Spec-Driven Testing
TestSprite is spec-driven. Plans are derived from what your product is supposed to do (your PRD), what the live app actually does (exploration / discovery), and the gap between the two. Uploading a PRD isn’t required, but it is strongly recommended. It’s how TestSprite builds an accurate feature map of your product before any test is written, and it directly improves the quality and coverage of the generated plan.
What It Tests
TestSprite covers two test types from the same dashboard:
| Test type | What it covers | Planned from |
|---|---|---|
| UI (frontend) — Playwright-driven, runs against a live URL | User-journey flows, form validation, visual states, stateful components, auth flows, UI error handling | A feature map built from your PRD plus Feature Exploration of your live app |
| API (backend) — Python-driven, runs against a base URL | Functional workflows, schema validation, auth flows, data integrity across calls, error handling, security | Your PRD plus OpenAPI / Swagger / Postman collections (or any free-form docs you upload) and live probes against the base URL |
How It Works
You provide a URL, credentials, and a PRD (strongly recommended). TestSprite builds a feature map from the PRD, explores or discovers your app, drafts a plan you can review, generates the tests, runs them in the cloud, and gives you a report. You can also refine the tests in natural language.1
Project Setup & PRD Upload
Click New Project, name the project, and provide your live URL and test-account credentials. For API projects, also provide your API documentation (OpenAPI / Swagger / Postman or any free-form docs). Then upload your PRD (or any product-spec document; markdown, PDF, and plain text all work) and add natural-language hints for what to focus on or skip. PRD upload is strongly recommended.
2
Explore or Discover
For UI, TestSprite walks your live app feature by feature. For API, TestSprite reads endpoints from your docs and probes the base URL to confirm shapes.
3
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 lifecycle; if you skipped the PRD, the map is built from what TestSprite explored or discovered alone.
4
Plan and Review
A test plan is drafted from the feature map + what was observed. You select / deselect / edit cases before generation runs.
5
Generate, Run, Report
Tests are generated and executed in our cloud. A run-level report highlights failures and suggests causes.
6
Refine and Schedule
Iterate on individual tests via Chats. Group tests into Test Lists. Schedule continuous runs to catch regressions.
Try it end-to-end
Walk through a complete project in about 15 minutes
Key Benefits
Different roles get different value out of the same dashboard:- For developers: Skip the test-writing boilerplate. Watch your changes get exercised against real flows in minutes, not hours. Iterate in natural language when something needs to be tightened.
- For QA teams: Replace handwritten regression suites with a plan TestSprite re-derives from your live app. Use Test Lists and Test Schedules to keep coverage running on a cadence.
- For engineering leads: Get reproducible reports, severity-ranked failures, and a defensible coverage story without standing up a test-writing organization.
What Makes It Different
Testing Capabilities
- UI Testing (Frontend)
- API Testing (Backend)
- PRD-driven Feature Map — features and use cases derived from your spec, rendered as a flow graph
- Feature Exploration — TestSprite walks your live app before any plan is written, targeting the use cases from the feature map
- Plan derived from spec + observed flows — grounded in both intent and reality
- Auto-Heal — recover automatically when the page changes instead of marking tests Failed
- Step-by-step replay — per-step screenshots + recorded video for every run
- Visual states, form flows, auth flows, error handling
- Generated code in Playwright + Python
What’s Inside the Dashboard
Where to Go Next
Your First Test
Walk through configuration to report end-to-end
Key Terms
Vocabulary used across the rest of the docs
Testing Lifecycle
The mental model behind TestSprite’s wizard
UI Testing
Start a UI project from scratch
API Testing
Start an API project from scratch
Join the Community
Discord for users and the team