> ## Documentation Index
> Fetch the complete documentation index at: https://docs.collabase.ch/llms.txt
> Use this file to discover all available pages before exploring further.
> Test cases define what to verify — each has a name, priority, type, status, and a set of ordered steps with expected results.
# Test cases
# Test Cases
A test case describes one thing to verify. It defines the steps a tester must follow and what they should observe at each step. Test cases belong to a Test Project and optionally to a Test Suite within that project.
Only test cases with a status of **READY** are included in test runs. Cases in DRAFT or DEPRECATED status are excluded.
## Test case fields
| Field | Required | Description |
| ---------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** | Yes | A short, action-oriented description. For example: "User can log in with valid credentials" or "Order confirmation email is sent after checkout." |
| **Description** | No | Additional context, preconditions, or background information for the tester. |
| **Priority** | Yes | Indicates how critical this case is. See priority levels below. |
| **Type** | Yes | Whether this case is MANUAL or AUTOMATED. See type descriptions below. |
| **Status** | — | DRAFT, READY, or DEPRECATED. Set automatically to DRAFT on creation. |
| **Linked Page** | No | A link to one page in Collabase Docs — typically a requirement, specification, or design document that this test case verifies. |
| **Linked Tasks** | No | One or more tasks in Collabase Projects that this test case covers. Use this to connect quality coverage to the work that implements the feature. |
## Priority levels
| Priority | Meaning |
| ------------ | --------------------------------------------------------------------------- |
| **Low** | Nice to have. Failure is acceptable in most releases. |
| **Medium** | Standard coverage. Should pass before release. |
| **High** | Important functionality. Failures block the release unless justified. |
| **Critical** | Core functionality or compliance requirement. Must pass before any release. |
## Test case types
| Type | Meaning |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Manual** | A tester must perform the steps by hand and observe the results. These cases are executed through Collabase's test run interface. |
| **Automated** | This case has automated test coverage in a CI/CD pipeline or test framework. The type is informational — it tells the team this case is covered externally. Automated cases still appear in test runs so their coverage is visible alongside manual cases, but execution results are typically recorded programmatically via the API rather than by a person. |
## Status lifecycle
| Status | Meaning |
| -------------- | -------------------------------------------------------------------------------- |
| **Draft** | The case is being written or has not yet been reviewed. Excluded from test runs. |
| **Ready** | The case has been reviewed and is approved for execution. Included in test runs. |
| **Deprecated** | The case is retired. Excluded from new test runs but preserved for history. |
```
Draft → Ready → Deprecated
```
Move a case from Draft to Ready once you are confident the steps are accurate and complete. Only Members and Owners can change a case's status.
## Test steps
Each test case contains an ordered list of steps. A step has two fields:
| Field | Description |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Action** | What the tester must do. Be specific and unambiguous. For example: "Click the Checkout button." |
| **Expected result** | What the tester should observe after performing the action. For example: "The payment form opens and the item summary is shown." |
Steps are numbered and executed in order during a test run.
## Creating a test case
Navigate to the Space → **Test Management** → click the test project.
Click **+ New Case** in the top bar. A creation form opens.
Enter the case name, select a priority, and select a type (Manual or Automated). Optionally assign it to a suite.
Add preconditions or context in the description field. This is shown to testers during the run.
Click **Save**. The case is created with a status of DRAFT.
## Adding test steps
Click the case name in the project case list to open its detail view.
Click the **Steps** tab in the case detail view.
Click **+ Add Step**. Enter the action and expected result for the first step.
Click **+ Add Step** again for each subsequent step. Steps are numbered automatically in the order they are added.
Drag steps to reorder them using the handle on the left side of each step row.
Steps are saved automatically as you add them.
## Linking tasks to a test case
Each test case can be linked to one or more tasks in Collabase Projects. This makes it easy to see which work items a test case covers — and from the task side, which test cases validate that work.
Click the case in the project list.
In the case sidebar, click **Linked Tasks**. A search box opens.
Type part of the task title or task key (for example, PROJ-42). Results appear as you type. Tasks from any project in the same space are included.
Click the task in the results list. It is added to the case immediately. Repeat for each additional task.
Click the × next to a linked task's name to remove it.
Once tasks are linked, they appear in the **Test Management** panel in the task detail view. Any team member with access to the task can see which test cases cover it without leaving the task context.
## Linking to a requirement page
Each test case can be linked to one page in Collabase Docs — typically a specification or requirement document that this case validates.
Click the case in the project list.
In the case sidebar, click **Linked Page**.
A page picker opens. Search by page title and select the page you want to link.
The link is saved immediately. Click the linked page name at any time to open it in Docs.
## Marking a case as Ready
Once you have written and reviewed a case, change its status to READY so it is included in test runs.
1. Open the case detail view.
2. Click the **Status** field in the sidebar.
3. Select **Ready**.
The case now appears with a READY badge and will be included in the next test run that covers this case or suite.
## Deprecating a case
When a test case no longer applies — because the feature was removed or the test was superseded — mark it as DEPRECATED rather than deleting it. This preserves its history in past runs while excluding it from future runs.
1. Open the case detail view.
2. Click the **Status** field.
3. Select **Deprecated**.
Deprecated cases remain visible in the case list with a DEPRECATED badge and can be filtered out using the status filter.