# Welcome to TestFirst **TestFirst** is a **full-stack QA platform** designed to help teams turn product knowledge into reliable test coverage. Start from requirements, generate structured test cases, automate workflows, and track results — all in one workspace. TestFirst supports the full testing lifecycle, from understanding requirements to generating tests, running tests, and reviewing results. You can start without writing code and expand into advanced automation as your testing needs grow. ### What you can do with TestFirst * Start testing directly from **requirements, specifications, or design documents** * **Generate AI-assisted test case drafts** * Refine test cases using the **TestFirst Editor or the Recorder** * Run automated tests **in the cloud** * Track **execution progress, failures, and results** You can begin without writing code, and gradually expand into more advanced automation workflows as your testing needs grow. ### Jump right in

		Cover image
Quickstart	Create, run, and review your first automated test case in minutes.	Hero Image.png	quickstart
Test Scopes	Organize requirements, generate tests, and manage testing for a feature or module.	Test Scope Window 1 (1).png	create-a-test-scope
Editor Basics	Learn how to write and edit tests using the TestFirst editor, selectors, and data repository.	Hero Image.png	editor-overview

## How TestFirst Works TestFirst organizes testing through a structured workflow built around three core components: **Test Scopes, Test Cases, and Test Execution**. Test Scopes define what needs to be tested, Test Cases describe the scenarios to verify, and Test Execution runs those tests and records the results, including outcomes and any defects found. At a high level, the platform follows this flow: ``` Test Scope ↓ Test Cases ↓ Test Execution ↓ Results & Issues ``` Each layer builds on the previous one and helps teams maintain structured and repeatable testing. *** ### Test Scopes A **Test Scope** defines the area of the product you want to test. It acts as the workspace where you: * organize test cases * generate tests from documentation * run tests and track results Scopes help keep testing focused on a specific feature, module, or release. ### Test Cases A **Test Case** describes a scenario you want to verify. Test cases can be: * generated from source documents * written manually * automated using the Recorder Test cases can also be reused from the **Test Case Library** across multiple scopes. ### Test Execution When tests are executed, TestFirst creates a **Test Plan** and records the results as a **Test Run**. Execution tracks: * pass or fail status * execution details * logs and artifacts from the run This makes it easy to monitor the quality of the system over time. ### Results and Issues After execution, you can review results and investigate failures. When problems are found, issues can be created and tracked directly from the testing workflow. This keeps testing results connected with development and debugging. *** ### How the Pieces Fit Together Most teams use TestFirst in a repeating cycle: ``` Define scope ↓ Add or generate tests ↓ Run tests ↓ Review results ↓ Improve tests ``` This cycle helps teams continuously expand and maintain reliable test coverage. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.testfirst.com/getting-started/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

:bolt:

:leaf:

:globe-pointer: