Yeah, those time-to-fix-bug numbers are definitely where TDD is going to shine. And that number probably only grows wider as a codebase grows. Codebases with good tests and good testing culture are going to improve or stay the same in this regard. Definitely not the case for the other kind.
Exactly, time-to-fix-bug is less because, in TDD, we should never write more production code than it is necessary to pass the currently failing unit test. This has profound implications. We don't have to think about the whole implementation upfront. We let the tests guide us.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, those time-to-fix-bug numbers are definitely where TDD is going to shine. And that number probably only grows wider as a codebase grows. Codebases with good tests and good testing culture are going to improve or stay the same in this regard. Definitely not the case for the other kind.
Exactly, time-to-fix-bug is less because, in TDD, we should never write more production code than it is necessary to pass the currently failing unit test. This has profound implications. We don't have to think about the whole implementation upfront. We let the tests guide us.