Workspace
The container everything else lives in. You have a personal workspace, and you can belong to team workspaces; the active one decides which projects you see. In a team workspace, each member has one role (Viewer, Member, Admin, or Owner). See Workspaces and Members & Roles.Project
One application under test, or one slice of it (a single micro-frontend or API surface). A project is either UI (frontend) or API (backend) and holds its configuration, tests, and run history. Create one with New Project on All Projects. See Test Detail Page.Test Case
A single executable check. UI tests are multi-step user journeys (sign in, navigate, fill a form, assert); API tests are usually per-endpoint checks (call, then assert status, schema, and contract). Each has a title, a natural-language description, steps, and after each run a status: Passed, Failed, or Blocked. They live on the project’s Test Cases page.Test Run
One execution of a set of tests. A run records a verdict per test, step-by-step screenshots and video (UI) or HTTP requests and responses (API), and a suggested cause and fix for each failure. Runs are listed on the project’s Test Runs page.Feature Map
The features of your product and the use cases under each, built from your PRD and what TestSprite explored or discovered. It’s what plans are scoped to. You’ll find it, and can edit it, on the project’s Test Coverage page. See Coverage Map.Test Plan
The test cases TestSprite’s testing agent plans from the feature map, before anything runs. You review, edit, add, or remove them in Review proposed tests, which opens after you click Plan Tests.Environment
A named target your tests run against, such as dev, staging, or production, with its own URL, sign-in details, and variable values. Switching environments changes where a run goes without touching the tests. See Environments.Test List
A reusable collection of tests, which can span projects: a regression suite, a smoke check, a release gate. A list has its own run history and is what you schedule. See Test Lists.Test Schedule
A rule that runs a Test List automatically on a cadence, in your team’s timezone. See Test Schedules.Credentials vs. API Keys
Easy to mix up:- Credentials are what TestSprite uses against your app: a test account for a UI project, or tokens and keys for an API project. They’re stored encrypted and set per environment.
- API keys authenticate you to TestSprite, for the CLI and MCP Server. See API Keys.