Test Management System — entity types

Complex QA is a classic test management system (TMS). You organize documentation in a team workspace, group work in projects, and execute tests through runs and results.

All documentation entities belong to a team and usually to a project.

Hierarchy

text

Team
 └── Project
      ├── Test suites (tree)
      │    └── Test cases
      │         └── Test case steps
      ├── Test accounts
      ├── Execution contexts (environment snapshots)
      ├── Bugs
      ├── Test runs
      │    └── Test run results (one per case in the run)
      └── (Tasks — aggregated view, not a separate entity)

Entity reference

Entity	Purpose	Key fields / statuses
Project	Top-level container for one product or release	`project_name`, `project_description`, `project_status`: `OPEN`, `CLOSED`
Test suite	Folder in a tree; groups related cases	`test_suite_name`, `parent_test_suite_id`
Test case	Documented test with steps and metadata	`test_case_title`, `test_case_status`: `PENDING`, `IN_PROGRESS`, `COMPLETED`, `CLOSED`; complexity and importance: `LOW`, `NORMAL`, `HIGH`
Test case step	Action and expected result for manual execution	`step_text`, `step_excepted_result`; types: `TEST_CASE_STEP`, `TEST_CASE_PRESTEP`
Test account	Credentials or environment data for testers	`resource`, `login`, `password`, `test_account_description`
Test run	Planned execution cycle	`test_run_name`, `test_run_status`: `PENDING`, `IN_PROGRESS`, `COMPLETED`, `CLOSED`
Execution context	Environment snapshot in the project	`context_title`, catalog axes, `host`, `base_url`, `build_version`
Bug	Defect in the project	`bug_title`, `bug_status`, `bug_priority`, `bug_severity`, `bug_type`
Test run result	Outcome of one case inside a run	`test_result_status`: `PENDING`, `PASSED`, `FAILED`, `SKIPPED`, `BLOCKED`, `RETEST`
Task	Your assigned work (runs, results, cases)	Filtered list, not stored separately

How entities connect

Suites and cases — Cases optionally sit in a suite. Suites nest via parent_test_suite_id. The project test structure API returns the full tree.
Runs and cases — Creating a run can copy all project cases (or a selected list) into test run results.
Assignment — assigned_to on a case, run, or result drives the Tasks view for that user.
Cloning — Suites and cases can be cloned (suite clone includes its cases; case clone includes steps).

What we do not have yet

To set expectations (compared to tools like TestRail):

No built-in automated test execution or CI report ingestion
No separate test type field on cases (types exist in config but are not linked to cases)
No project config templates on the current project model
Invite by email only adds users who already registered (no pending invite mail)

Detail pages


Version	1.1
Last updated	2026-06-13

Test Management System — entity types ​

Hierarchy ​

Entity reference ​

How entities connect ​