Element reference

Test case

Test case

A test case describes what to verify in a project. It can include preconditions, steps, and an expected result. Cases without a suite sit at the root of the project catalog.

Relations

Related elementHow it connects
ProjectRequired owner of the case
Test suiteOptional parent in the suite tree
Test case stepOrdered steps of the case
BugOptional links on the case Bugs tab
Test run resultCreated when the case is included in a test run
Custom propertiesTeam-defined slots on the case details page

Fields

LabelTechnical nameTypeRequiredValidationDefault
Titletest_case_titlestringYesMax 90 characters-
Descriptiontest_case_descriptionHTMLNoMax 350 characters-
Statustest_case_statusenumYesSee enumerations-
Complexitytest_case_complexityenumNoLOW, NORMAL, HIGH-
Importancetest_case_importanceenumNoLOW, NORMAL, HIGH-
Time to executetest_case_time_to_executeintegerNoEstimated minutes-
PreconditionspreconditionsHTMLNoMax 2900 characters-
Expected resultexpected_resultHTMLNoMax 2900 characters-
Suitetest_suite_ididNoSuite in the same project-
Assigneeassigned_touser idNoShown in Tasks when status is open-

Enumerations

Status (test_case_status)

ValueMeaning
PENDINGNot started
IN_PROGRESSBeing written or prepared
COMPLETEDReady for execution
CLOSEDNo longer used

Rules

  • Clone case copies the case and all its steps.
  • Delete removes the case and its steps. Results for that case are removed from all test runs in the team; the runs themselves stay.
  • Custom property slots come from the team catalog. Empty slots stay visible. You cannot add ad-hoc fields on the case.
  • Optional text fields (description, preconditions, expected result) can be cleared after they already had text. Saving an empty value leaves the field empty.

Limits

Version 1.2.0 · Last updated 2026-09-15

Did this page help?