Skip to content
SyntaxisSyntaxisSyntaxis

test-cases

Designs test cases into syntaxis/qa/cases/<area>.md.

Invocation

Section titled “Invocation”
/test-cases              cases for the active work
/test-cases 7            cases for build-plan item 7
/test-cases checkout     cases for a named area
/test-cases regression   assemble a regression set from existing cases

Coverage

Section titled “Coverage”

Each requirement gets the expected path, boundaries, invalid input, state and permission, and interruption. Mobile surfaces add permissions, background and resume, offline, rotation, display sizes, and call interruption — for targeted platforms only.

What it guarantees

Section titled “What it guarantees”
  • Cases derive from requirements, not from the implementation.
  • Every case names what it covers; a case that covers nothing is not a case.
  • One observable expected result per case. “Works correctly” is not one.
  • Identifiers are durable: never reused, never renumbered, retired not deleted.
  • Untestable requirements are reported as such rather than given hollow cases.
  • It never marks a case automated; /automate owns that.

See Test Design.