agentleFS
tusharranjan-aitusharranjan-ai/testronaut/.claude/skills/test-design/SKILL.md

test-design

Skill2 starsChanged 3 months agoMITView on GitHub

Draft executable test cases from approved requirements plus the OpenAPI spec. One invocation per endpoint.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use diff-review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MidnightDarlingSkill

    diff-review

    使用场景:按 raw.review.md 清单改完稿后,对 raw.md(OCR 原始)和 final.md(定稿)做对比。说"看我改了哪些""对比一下""diff""校对完了让我看看""我到底接受了哪些建议""我漏改了啥""改动统计""核对一下改动""闭环检查"都走这个 skill。生成段落级 HTML diff,关联 raw.review.md 的 A/B/C 标注,一目了然:接受了哪些 agent 建议、拒绝了哪些、清单外修正了哪些、agent 标过但漏改了哪些。主动触发,不必等用户说 "diff-review"。

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every case exists to exercise a requirement — if you cannot name the requirement, do not write the case.

    line 11
  2. Very specific:

    Every case links to at least one approved req_id via requirement_ids.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Design

Draft test cases for one endpoint from its approved requirements and the spec.

Requirements say what must hold; a test case says how you would demonstrate it. Every case exists to exercise a requirement — if you cannot name the requirement, do not write the case.

Rules

  1. Every case links to at least one approved req_id via requirement_ids.
  2. Cover every approved requirement with at least one case. An uncovered requirement is a gap the traceability check will report.
  3. expected_status must be a status code the spec declares for this operation. This is enforced; a status the spec does not declare is rejected.
  4. category must be one of happy_path, negative, boundary, auth, security, and must have been requested for this run. Also enforced.
  5. Inputs — path_params, query_params, headers, body — must be valid per the spec: real parameter names, real types, required fields present. A negative case breaks exactly one rule on purpose and states which.
  6. expected_body holds assertions in the grammar below, one claim per entry. Prose is not compiled into the generated test — it survives only as a TODO comment a human has to finish, so an assertion you can express in the grammar is worth far more than one you cannot.
  7. test_data_notes says what real data the operator must supply — "a petId that exists in the store", not "user provides data".
  8. preconditions are things that must be true before the request, not steps.
  9. Priority inherits from the requirement unless the case is a narrower edge of it.

Assertion grammar

expected_body entries must be one of these six forms. $. addresses the response body; $.a.b[0].c walks nested objects and arrays.

$.path == value            $.id == 5          $.name == 'Fluffy'
$.path != value            $.code != 500
$.path contains 'text'     $.message contains 'required'
$.path exists              $.id exists
$.path matches /regex/     $.name matches /^[A-Z]/
$.array length == N        $.tags length == 2

Assert what the spec's response schema actually promises. Do not assert on a field the schema does not declare.

IDs

case_id is TC-<OPTOKEN>-<NNN>, numbered from 001 within this endpoint, using the OPTOKEN given to you. Duplicate IDs within a run are rejected.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.