Test Case Authoring

Write the tests for one work item so the QA notes on the ticket have real content and the fix verification on a bug names a real test. Tool-agnostic: works with any test runner, any tracker, and any test management tool.

When to use

• A story is ready and its acceptance criteria need test cases
• A bug fix needs a named verification test and a regression set
• QA notes on a ticket say "test it" and nothing else
• Checking whether a set of acceptance criteria is testable at all
• A spike needs an exploratory charter instead of pass/fail cases
• A coding agent will run the tests and needs to know what evidence to return

When NOT to use