I've not had any horror stories per se. But for me it really depends a lot in which context one tries to do TDD, how successful it turn out. For me it's relatively easy in the business layer when you have clear specifications of how a feature should work. I think it's harder, in an Angular client if you for example do a proof of concept to have something to reason about with the client.
But. It is in those cases, where the specifications is not that clear, is where TDD in a way shines. Because it forces you to really think about what the end goal really is. So in that way, it can be a tool that can help formulate questions you need answered to be able to complete the feature.
I would very much like to use TDD in every instance possible. But how low the threshold is to get started, comes down to, as other have stated, how an application in configured.
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.
I've not had any horror stories per se. But for me it really depends a lot in which context one tries to do TDD, how successful it turn out. For me it's relatively easy in the business layer when you have clear specifications of how a feature should work. I think it's harder, in an Angular client if you for example do a proof of concept to have something to reason about with the client.
But. It is in those cases, where the specifications is not that clear, is where TDD in a way shines. Because it forces you to really think about what the end goal really is. So in that way, it can be a tool that can help formulate questions you need answered to be able to complete the feature.
I would very much like to use TDD in every instance possible. But how low the threshold is to get started, comes down to, as other have stated, how an application in configured.