tdd

You can enforce a TDD workflow by following a guided Red-Green-Refactor cycle for every code change. This approach ensures you write a failing test first, implement minimal code to pass, and then refactor to maintain robust and maintainable software.

Yes, the TDD workflow supports automatic stack detection to identify the correct testing framework. It automatically detects Vitest, pytest, and pytest-django based on the code location of your UI, SDK, or API components.

The Red-Green-Refactor cycle is a Test-Driven Development process where you write a failing test, implement minimal code to pass, and then refactor. You need it to reduce bugs, ensure code quality, and enable confident refactoring.

To start writing a new feature, you first write a failing test that defines the desired functionality. Then, you implement the minimal code required to make that test pass before refactoring the implementation for better code quality.

Yes, you can use this workflow to refactor existing code safely. By enforcing the test-driven development cycle, the workflow ensures your code remains robust and maintainable, enabling confident refactoring across all components.

Automated TDD stack detection is limited to Vitest, pytest, and pytest-django frameworks. It operates by identifying the correct testing framework based on your code location across UI, SDK, and API components.