CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/test-case-anatomy-reference

Pure-reference catalog of test-case anatomy - what fields a well-formed test case must have and what each field means. Enumerates the ISO/IEC/IEEE 29119-3:2021 test-case template fields (identifier, objective, preconditions, inputs, steps, expected results, postconditions, environment, traceability) and the ISTQB CTAL-TM specification-technique-driven additions (equivalence partition, boundary value, decision table, state transition). Maps the canonical anatomy to five tracker-specific schemas (TestRail, Xray, Zephyr Scale, Allure TestOps, Qase). Use as the authoritative source when authoring a case template, reviewing case quality, or migrating between tools.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

tracker-schema-map.mdreferences/

Tracker-schema map

Five common trackers each store the canonical test-case anatomy under different field names. Use this map when migrating cases between tools or when a template author must know the exact per-tracker field to write to. Sources for each tracker's API are listed in the parent SKILL.md References section.

TestRail

Canonical fieldTestRail field
Identifierid (e.g., C1234)
Objectivetitle
Preconditionscustom_preconds
Inputs(within custom_steps_separated[].content)
Stepscustom_steps_separated (Steps template) or custom_steps (Text template)
Expected resultscustom_steps_separated[].expected
Postconditions(custom field if defined)
Environmentcustom_environment (custom field) or filter via refs
Traceabilityrefs (free text); template_id (Steps / Text / Exploratory)

TestRail templates (template_id): Steps (1) / Text (2) / Exploratory (3). The Steps template enforces step-level structure; Text is freeform; Exploratory is for SBTM-style charters.

Xray (Atlassian)

Xray stores tests as Jira issues with Test issue type. Steps live in a separate sub-entity.

Canonical fieldXray field
IdentifierJira key (e.g., ENG-123)
ObjectiveJira summary
PreconditionsLinked precondition (separate Jira issue type)
StepsTest steps section (per testType: Manual); for Cucumber, Gherkin section; for Generic, free-text
Expected resultsper-step expectedResult
EnvironmentTest execution testEnvironments (set per run)
TraceabilityJira issue links (Tests / TestedBy)

Xray testType: Manual / Cucumber / Generic. Determines how steps are stored.

Zephyr Scale (Smart Bear)

Canonical fieldZephyr field
Identifierkey (e.g., PROJ-T123)
Objectivename
Preconditionsprecondition
StepstestScript.steps[].description
Expected resultstestScript.steps[].expectedResult
EnvironmentConfigured per test cycle, not case
TraceabilityissueLinks (Jira issues)

Allure TestOps

Canonical fieldAllure TestOps field
Identifierid (numeric, e.g., 1234)
Objectivename
Preconditionsprecondition
Stepsscenario.steps (recursive - steps can have sub-steps)
Expected resultsWithin step expectedResult
Environmenttags (key=value pairs) + execution env
Traceabilityrelations (links to other cases / requirements)

Qase

Canonical fieldQase field
Identifierid (within project; full ID is PROJ-1234)
Objectivetitle
Preconditionspreconditions
Stepssteps[].action
Expected resultssteps[].expected_result
EnvironmentCustom fields
Traceabilitylinks field

Severity, priority, type (cross-platform)

All five trackers carry severity / priority / type fields. Each uses its own enum but they map similarly:

ConceptTestRailXrayZephyr ScaleAllure TestOpsQase
Prioritypriority_id (1-4)Jira priority fieldpriority enumCustompriority enum (low/med/high)
SeverityCustom fieldCustom fieldseverity enum (minor/normal/major/critical/blocker)severity (default labels)severity enum
Typetype_id (Functional, Performance, etc.)testType (Manual/Cucumber/Generic)testType (Manual/Automated)Customtype (functional/smoke/regression/etc.)
Automation statuscustom_automation_typeLinked to automation resultsautomation fieldTagsautomation (manual/automated/to-be-automated)

SKILL.md

tile.json