Test cases and suites
Test suites organize your catalog. Test cases describe what to verify, with optional steps, preconditions, and expected results.
Both belong to a project and team.
Test suites
Suites form a tree: each suite can have a parent_test_suite_id. Cases without a suite appear at the root of the structure.
Fields
| Attribute | Type | Rules |
|---|---|---|
test_suite_name | string | Max 250; default name new suite if empty |
test_suite_description | HTML | Max 900 characters |
parent_test_suite_id | id | Optional — parent suite |
project_id | id | Required |
Actions
- Create, rename, and nest suites in the project test-case view.
- Clone suite — duplicates the suite and all cases inside it (cases point to the new suite).
Test cases
Fields
| Attribute | Type | Rules |
|---|---|---|
test_case_title | string | Max 90 characters |
test_case_description | HTML | Max 350 characters |
test_case_status | enum | See below |
test_case_complexity | enum | LOW, NORMAL, HIGH |
test_case_importance | enum | LOW, NORMAL, HIGH |
test_case_time_to_execute | integer | Estimated minutes |
preconditions | HTML | Max 2900 characters |
excepted_result | HTML | Max 2900 characters (field name in the system) |
test_suite_id | id | Optional |
assigned_to | user id | Optional — shows in Tasks when status is open |
Case statuses
| Status | Typical use |
|---|---|
PENDING | Not started |
IN_PROGRESS | Being written or prepared |
COMPLETED | Ready for execution |
CLOSED | No longer used |
Actions
- Create and edit cases in the listing / details UI.
- Clone case — copies the case and all its steps.
- Delete removes the case and its steps.
Test case steps
Steps describe manual execution. They are ordered by sort_order.
Step types
| Type | Role |
|---|---|
TEST_CASE_PRESTEP | Preconditions shown as pre-steps |
TEST_CASE_STEP | Main test steps |
Step fields
| Attribute | Max length |
|---|---|
step_text | 5000 (HTML) |
step_element | 900 |
step_element_action | 900 (HTML) |
step_excepted_result | 900 (HTML) |
You can reorder steps with increase / decrease sort order actions in the API.
UI automation hints (configuration only)
The system exposes configuration for step targeting and actions (for example id, css, click, load_page). These are metadata for future automation; the TMS does not run automated scripts today.
Building structure
Recommended order:
- Create top-level suites (modules, features, or releases).
- Add child suites where needed.
- Add test cases under the right suite.
- Fill steps, preconditions, and expected result before the first test run.
Use Get test structure (project API) or the in-app tree to review the full hierarchy.
Related
- Test runs — execute selected cases
- Entity overview
| Version | 1.0 |
| Last updated | 2026-06-06 |