Many companies try to introduce TDD through a 2-5 day TDD Training Program. But the foundational skillsets in Effective Tests and Effective Code are missing. TDD then doesn't work! How to solve this?
Thanks for this insightful article. I'm wondering, though, if testable architecture is a must-have to start TDD. I've got the feeling that with the right tools (I'm thinking about insights from the book "Working Effectively with Legacy Code"), we can make the legacy code testable (without having transitioned to a hexagonal or clean architecture). Therefore, we can apply TDD on the slightly modified version of the code (provided we know how to write effective tests and effective code, I agree on that).
Thanks for this insightful article. I'm wondering, though, if testable architecture is a must-have to start TDD. I've got the feeling that with the right tools (I'm thinking about insights from the book "Working Effectively with Legacy Code"), we can make the legacy code testable (without having transitioned to a hexagonal or clean architecture). Therefore, we can apply TDD on the slightly modified version of the code (provided we know how to write effective tests and effective code, I agree on that).
What are your thoughts about that?