
PRD Upload
Your product requirements doc. Features, use cases, and test coverage are generated directly from it.
API Doc Upload
An OpenAPI/Swagger spec, or any doc listing your endpoints. Backend only — auto-discovers endpoints for you to review before testing starts.
Agent Web Exploration
TestSprite’s agent browses your live frontend and clicks through flows on its own. Runs automatically after you create a Frontend project; re-run anytime.
Test Files (Fixtures)
Beta Files the agent attaches when a test hits a file-upload field.

Test Files
Beta. Not every plan includes Test Files. Compare plans on the pricing page.
Adding a Source Later
You’re not limited to what you add at project creation. Go to Setup → Sources and click + Add Source to upload more sources at any point. The same page also shows your Live Site Exploration status and every page it’s captured so far.
Endpoint Discovery & Selection
For Backend projects, endpoints only come from an uploaded API doc — there’s no separate crawl or agent-exploration path to discover them. After upload, TestSprite parses the doc and shows every discovered endpoint in a reviewable list where you can remove ones you don’t want tested, add endpoints manually, or fix flagged coverage gaps (e.g. a resource with no matchingPOST) before saving.
Combining Sources
The most common pairing is PRD + Agent web exploration: the PRD drives what gets generated, and exploration fills in how the app actually behaves. For Backend projects, API doc is the source endpoint tests are generated from, with PRD still driving feature-level coverage alongside it.Where to Go Next
Run Behavior
Configure how your tests run once sources are in place
Environments
Define environment variables and run against dev/staging/prod
Feature Exploration
How TestSprite explores your live app feature by feature
Your First Test
Haven’t created a project yet? Start here