tdd

Test-Driven Development for Svelte components follows the Red-Green-Refactor cycle: write a failing test, implement minimal code to pass it, then refactor. This Skill guides you through each phase using pnpm for automated test execution and verification.

The Red-Green-Refactor workflow in TDD means writing a failing test first (Red), writing minimal implementation code to make it pass (Green), and then cleaning up the code without changing behavior (Refactor) for maintainable Svelte components.

Yes, this TDD workflow supports the Svelte v5 Runes API. It guides you through defining test structures and writing minimal code specifically for Svelte components built with the latest Runes reactivity model.

You run tests during TDD with pnpm by executing the pnpm test command. The workflow integrates automated test execution to verify outcomes after writing failing tests and after implementing minimal code changes.

You should use TDD for developing new features when you want to ensure robust functionality and clean, maintainable code. It is particularly effective when building new Svelte components where defining expected behavior upfront prevents regressions.

TDD refactoring improves code quality in Svelte applications by encouraging you to clean up and restructure code after tests pass. This ensures the implementation remains maintainable without altering the verified behavior defined by the tests.