CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/test-case-anatomy-reference

Pure-reference catalog of test-case anatomy and review quality - what fields a well-formed test case must have, what each field means, and how to score the content once the fields are filled. 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), and carries the review rubric: six per-case quality axes plus six set-level axes with PASS / WEAK / FAIL verdicts derived without averaging, each threshold marked standard-backed or practitioner convention. Use as the authoritative source when authoring a case template, reviewing a batch of test cases for quality, or migrating between tools.

70

Quality

88%

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

77%Weight 40%Scale 1-5

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

A well-structured reference skill with strong workflow gating and clean progressive disclosure into two real reference files. Its main weakness is conciseness - several conventions and rules are restated across multiple sections.

Suggestions

Consolidate the step-count ceiling, never-average rule, and convention-vs-standard distinctions so each appears once; cross-reference rather than restating them across the rubric, Conventions, Judgment calls, and Anti-patterns sections.

The worked example in the body overlaps conceptually with references/review-rubric-worked-examples.md; consider shortening the inline example to a one-paragraph pointer to avoid duplicating the before/after treatment.

Trim the 'How to use' and 'When to use' sections, which overlap with the Overview and could merge into a single concise entry path.

DimensionReasoningScore

Conciseness

Mostly efficient dense reference tables assuming domain familiarity, but there is noticeable repetition - the never-average rule, step-count ceiling, and convention-vs-standard distinctions each recur across the rubric, conventions, judgment calls, and anti-patterns sections and could be tightened.

3 / 5

Actionability

Provides concrete, copy-ready guidance - per-axis PASS/FAIL bars, a field cardinality table, anti-pattern fixes, and a worked 'test checkout' to C1051 rewrite - though the full tracker field maps and worked examples are deferred to reference files.

4 / 5

Workflow Clarity

A clear 7-step 'How to use' sequence is gated by an explicit Gate 0 validation checkpoint with feedback loops (UNSCORABLE returned to author, fix-before-done, rewrite-before-execution) and checklists (nine-field table, anti-patterns table) for a batch review operation.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview that keeps the core anatomy and rubric inline while pushing the tracker-schema map and worked examples to one-level-deep, well-signaled reference files (both verified to exist) with explicit links.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 precise, third-person reference description that explicitly states both capability and usage triggers, anchored to named standards and tools. It is somewhat verbose, but verbosity does not undermine specificity or completeness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - enumerating the nine ISO fields, mapping to five named tracker schemas, and carrying a rubric of six per-case and six set-level axes - giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (catalog of anatomy and review rubric, field enumeration, tracker mapping) and 'when' ('Use as the authoritative source when authoring a case template, reviewing a batch of test cases for quality, or migrating between tools').

5 / 5

Trigger Term Quality

Includes natural trigger phrases like 'authoring a case template', 'reviewing a batch of test cases for quality', and 'migrating between tools' plus tracker names, but a few common synonyms and bare file/term variants are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche - test-case anatomy and review quality tied to ISO 29119-3 and ISTQB with named tracker schemas - with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

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