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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured pure-reference skill: dense tables, a sequenced how-to with a validation checkpoint, and a single clearly-signaled reference file for tracker-specific detail. It is concise and immediately actionable.

DimensionReasoningScore

Conciseness

Lean, table-driven reference with no padding of concepts Claude already knows; every section (canonical fields, cardinality, anti-patterns) earns its tokens.

3 / 3

Actionability

Gives concrete per-tracker field names and a fully worked example with literal values (C1051, alice@example.com, SKU WIDGET-1, coupon SAVE10) — actionable instruction-only guidance, not pseudocode.

3 / 3

Workflow Clarity

The 7-step 'How to use' sequence is explicitly ordered with a validation checkpoint — step 6 runs the draft past the anti-patterns table and fixes matches 'before the case is considered done'.

3 / 3

Progressive Disclosure

Overview points to a single one-level-deep reference ([references/tracker-schema-map.md], verified present) for the bulky per-tracker detail, with clearly signaled links and well-organized sections.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, third-person description that states concrete capabilities and gives explicit use-when triggers tied to authoring, reviewing, and migrating test cases. It is distinctive and free of fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — 'Enumerates the ISO/IEC/IEEE 29119-3:2021 test-case template fields' and 'Maps the canonical anatomy to five tracker-specific schemas' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Pure-reference catalog... Enumerates... Maps...') and when ('Use as the authoritative source when authoring a case template, reviewing case quality, or migrating between tools').

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'authoring a case template, reviewing case quality, or migrating between tools' plus the named trackers (TestRail, Xray, Zephyr Scale, Allure TestOps, Qase).

3 / 3

Distinctiveness Conflict Risk

A clear niche — canonical test-case anatomy mapped to five specific trackers — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents