Test-Driven Development

Write the behavior case first. Watch the test fail for the right reason. Then write the smallest useful code to make it pass.

This is an implementation skill, not the place to design a whole test suite. Use high-level-testing-strategy first when test cases or scope are unclear.

Testing Skill Map

high-level-testing-strategy
  -> architecting-test-infra       (if framework/fixtures/state/env are weak)
  -> test-driven-development       (you are here: automated implementation)
       -> manual-testing           (if runtime/e2e/smoke proof is still needed)
  -> verification-before-completion