> For the complete documentation index, see [llms.txt](https://docs.testfirst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testfirst.com/test-scopes/test-scopes-overview.md).

# Test Scopes Overview

```
Test Scopes generate coverage and draft test cases from source documents.
```

A **Test Scope** is the workspace in TestFirst used to define and manage testing for a specific feature, module, or release item. Within a scope, teams can collect product context, generate test coverage, manage test cases, and execute tests in one place.

A Test Scope represents a **complete testing package** for any functional unit of work.

## What You Can Do in a Test Scope

Within a Test Scope you can:

* Upload requirement or design documents
* Generate **test coverage** and draft test cases
* Combine generated tests with items from the **Test Case Library** 
* Organize tests into suites or sections
* Run tests and track execution results

This keeps all testing activities for a feature organized within a single workspace.

## Coverage and Test Cases

When TestFirst analyzes source files, it generates **test coverage** for the feature being tested.

Coverage represents the set of behaviors, flows, and scenarios identified in the uploaded requirements or design documents. From this coverage, TestFirst creates draft test cases that verify those scenarios.

Coverage helps teams understand:

* which parts of a feature are already tested
* which scenarios may still require additional tests
* how complete the testing is for that scope

This makes it easier to track testing progress at the **feature or release level**.

***

### Typical Workflow

Testing within a scope usually follows this cycle:

```
Add Product Context(Source Files)
   ↓
Generate Coverage and Draft Test Cases
   ↓
Review and Select Test Cases
   ↓
Record/ Write Test Cases
   ↓
Run Tests
   ↓
Review Results
```

As development evolves, scopes can be updated and executed again to maintain reliable coverage.

### When to Use Test Scopes

Use a Test Scope whenever you want to organize testing for a specific unit of work, such as:

* a new feature
* a product module
* a release or regression cycle
* a bug fix or improvement

Scopes keep related requirements, coverage, tests, and results connected.