Organizing at Scale

Organizing test cases helps maintain clarity, structure, and scalability as your repository grows.

In TestDino, organization happens through suites and tags, allowing both hierarchical and cross-sectional grouping.

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.

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.

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 let you perform actions on multiple test cases at once. Use the checkboxes beside test case rows in list/grid View to select more than 1 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:

Reorder Suite: This allows you to change the sequence of suites within the same hierarchy level, but cannot be moved across different parent suites.

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.

Delete Suites: Permanently delete the selected suites. Deleted suites cannot be recovered.
Expand/Collapse: Toggle the visibility of nested suites when managing multiple levels simultaneously.

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:

Move to Suite: Reassign selected test cases to another suite or subsuite.
Change Description: Update the description for all selected cases.
Change Precondition / Postcondition: Update these fields for all selected cases.
Change Classifications: Batch update Status, Severity, Type, Layer, or Behavior.
Change Automation Status: Batch update Manual/Automated status and flags (To Be Automated).

Blank fields are ignored, and existing data remains unchanged.

Add/Remove Tags: Add new tags, remove all tags, or keep existing tags for the selected cases.
Delete: Permanently delete all selected test cases. Deleted test cases cannot be recovered.

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

Creating & Editing Import & Export