|
|
|
|
|
by sevenadrian
4917 days ago
|
|
I think this is the comment I agree with the most so far. I believe TDD is important, especially for a MVP one could argue. Do MVPs change a lot? Yes, obviously because you are learning and adapting to the needs of you customers. This is where have good test coverage (thanks to TDD) is a big asset. You can refactor, change, pivot, all you want, without the worry that removing this feature, tweaking that feature, or adding this other feature, won't break something else. And manual testing is way more expensive then investing in automated testing. In my opinion, unless it is a very short lived project that you don't plan to iterate on and isn't very important, you should have good test coverage. And good test coverage is best achieved with TDD. This is of course just my 2 coins |
|