[Feature Request] Improved TDD support and test-driven development workflow enforcement
Bug Description
I'm so frustrated with Claude's inability to do TDD. TDD is absolutely necessary when writing code this way, because the system will just decide it's done good work while making tests pass alongside of writing code. Might as well not do any kind of test at all. As Claude writes code now, the only way I've found to make maintainable code is to write in TDD, but I have to remind Claude in every single stage that it needs to be careful to write maintainable code that meets specific behavioral expectations. It _always_ ignores this directive. It's just so frustrating.
I also have to keep telling Claude that red tests are not compilation failures, they aren't todos or panics in the tests, but are because an asserted expected behavior is not met. It _keeps_ forgetting this definition as well, and just writes test theater filled with panics, todos, or calls a failing compilation a red test.
Environment Info
- Platform: linux
- Terminal: gnome-terminal
- Version: 2.1.119
- Feedback ID: a1636c20-a36e-400e-b661-17a38d735933
Note: Content was truncated.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗