> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizing Test Cases at Scale

> Scale your test case repository in TestDino using suites, tags, and bulk operations. Maintain structure as your test suite grows to hundreds of cases.

Organize test cases using **suites** for hierarchical grouping and **tags** for cross-sectional categorization.

## Suite Assignment and Hierarchy

The primary method of organization is the suite hierarchy. Suites represent logical areas such as features, modules, or workflows, and can contain nested **subsuites** for deeper structure.

Create suites and subsuites that mirror your application's logical structure. Place new test cases into the most relevant suite.

### Using Tags for Cross-Suite Organization

Tags provide a flexible, secondary organization system that works across suites. Tags solve problems that hierarchies cannot.

* **For example**, you may have "Smoke" tests in many different feature suites (Login, Payments, Search).

* A hierarchy cannot group them, but a smoke tag can.

* Add tags like smoke, regression, p1, or v2-feature to test cases.

* You can then use the **Tags filter** to find all test cases with that tag, regardless of their suite.

<Callout icon="lightbulb" color="#10B981">
  **Note**

  * Each test case can have multiple tags.
  * Tags can be created on the fly while editing a test case.
  * You can apply tags in bulk or during import.
</Callout>

### Suite vs Tags: When to Use What

Using both correctly keeps your test repository searchable, scalable, and intuitive.

| Use Case                               | Choose    | Why                                                                   |
| -------------------------------------- | --------- | --------------------------------------------------------------------- |
| Grouping tests by feature or component | **Suite** | Suites represent structure and ownership.                             |
| Grouping across releases or builds     | **Tag**   | Tags cross suites and help track test coverage per version.           |
| Managing different test types          | **Tag**   | Add "Smoke", "Regression", or "End-to-End" tags to mix across suites. |
| Permanent categorization               | **Suite** | Suites persist as long-term organizational containers.                |
| Temporary or cross-cutting tracking    | **Tag**   | Ideal for temporary campaigns or sprints.                             |

## Bulk Operations

Bulk operations apply actions to multiple test cases at once. Use the **checkboxes** beside test case rows in list/grid view to select more than one test case.

Alternatively, you can also select all test cases in that particular suite from the table header.

### Suites

When suites are selected from the sidebar, action buttons appear, such as Delete suites and Clear.

The following operations can be performed:

1. **Reorder Suite:** Change the sequence of suites within the same hierarchy level. Suites cannot be moved across different parent suites.

<Callout icon="circle-info" color="#3B82F6">
  **Note**

  * You can reorder root-level suites with each other.
  * You can reorder sub-suites only within the same parent suite.
  * You cannot drag a subsuite to a different parent suite.
  * Similarly, if a subsuite contains nested suites, you cannot reorder it outside its immediate hierarchy.
  * Each level (root, subsuite, nested subsuite) maintains its own independent reorder scope.
</Callout>

2. **Delete Suites:** Permanently delete the selected suites. Deleted suites cannot be recovered.

3. **Expand/Collapse:** Toggle the visibility of nested suites when managing multiple levels simultaneously.

<video controls loop preload="metadata" aria-label="Bulk suite actions reordering, deleting, and expanding selected suites" src="https://tdstorageus.blob.core.windows.net/public/docs/_unlisted/test-management/test-case/organizing-at-scale/bulk-operations-suites.mp4" />

### Test Cases

When test cases are selected in List or Grid view, action buttons appear, such as Edit, Delete, and Clear.

The following actions are available:

1. **Move to Suite**: Reassign selected test cases to another suite or subsuite.

2. **Change Description**: Update the description for all selected cases.

3. **Change Precondition / Postcondition**: Update these fields for all selected cases.

4. **Change Classifications**: Batch update Status, Severity, Type, Layer, or Behavior.

5. **Change Automation Status**: Batch update Manual or Automated status and flags (`Is Flaky`, `Is Muted`).

<Callout icon="circle-info" color="#3B82F6">
  **Note**

  Blank fields are ignored, and existing data remains unchanged.
</Callout>

6. **Add/Remove Tags**: Add new tags, remove all tags, or keep existing tags for the selected cases.

7. **Delete**: Permanently delete all selected test cases. Deleted test cases cannot be recovered.

<video controls loop preload="metadata" aria-label="Bulk test case actions moving to a suite, changing classifications, and editing tags" src="https://tdstorageus.blob.core.windows.net/public/docs/_unlisted/test-management/test-case/organizing-at-scale/bulk-operation-tests.mp4" />

<Callout icon="triangle-exclamation" color="#F59E0B">
  **Warning**

  In bulk operation, a maximum of 200 items can be edited/deleted at a time.
</Callout>

## Related

<CardGroup cols={2}>
  <Card title="Test Suites" icon="folder-tree" href="/test-management/suites">
    Create and manage suite hierarchy
  </Card>

  <Card title="Test Case Structure" icon="flask" href="/test-management/test-case/structure">
    Fields, steps, custom fields, and attachments
  </Card>

  <Card title="Creating & Editing" icon="pen-to-square" href="/test-management/test-case/creating-editing">
    Three creation methods and inline editing
  </Card>

  <Card title="Import & Export" icon="file-import" href="/test-management/import-export">
    Bulk import from CSV or TestRail
  </Card>
</CardGroup>