cycle

RED+GREEN+REFACTOR (one cycle) PHASE! Apply the below to the info given by user input here: $ARGUMENTS

(If there was no info above, fallback to the context of the conversation)

TDD Fundamentals

The TDD Cycle

The foundation of TDD is the Red-Green-Refactor cycle:

1. Red Phase: Write ONE failing test that describes desired behavior

   • The test must fail for the RIGHT reason (not syntax/import errors)
   • Only one test at a time - this is critical for TDD discipline
     • Exception: For browser-level tests or expensive setup (e.g., Storybook *.stories.tsx), group multiple assertions within a single test block to avoid redundant setup - but only when adding assertions to an existing interaction flow. If new user interactions are required, still create a new test. Split files by category if they exceed ~1000 lines.
   • Adding a single test to a test file is ALWAYS allowed - no prior test output needed
   • Starting TDD for a new feature is always valid, even if test output shows unrelated work
   • Avoid hard-coded timeouts both in form of sleep() or timeout: 5000 etc; use proper async patterns (waitFor, findBy*, event-based sync) instead and rely on global test configs for timeout settings

2. Green Phase: Write MINIMAL code to make the test pass

   • Implement only what's needed for the current failing test
   • No anticipatory coding or extra features
   • Address the specific failure message

3. Refactor Phase: Improve code structure while keeping tests green

   • Only allowed when relevant tests are passing
   • Requires proof that tests have been run and are green
   • Applies to BOTH implementation and test code
   • No refactoring with failing tests - fix them first

Core Violations

1. Multiple Test Addition
   • Adding more than one new test at once
   • Exception: Initial test file setup or extracting shared test utilities