The Cost of Skipping TDD and Code Reviews (2016)

Re:The Cost of Skipping TDD and Code Reviews (2016) by heisenbit on Monday September 11, 2017 @02:11AM (#15216351)

Of course catching bugs early is much, much better and well executed code reviews and TDD are the way to go.

But what do you do if your team struggles to get the basics right? When asking them to write tests results in doubling the code base with trivial module tests finding no bugs and only preventing the all too necessary refactoring? Slowing the team down so much it has to be scaled up? What if the software is not intended to live long?

What if manual tests are the fastest and most reliable way to establish feedback?

[ Parent | on HN ]

Re:The Cost of Skipping TDD and Code Reviews (2016) by clu3l355 on Monday September 11, 2017 @05:36AM (#15217216)

Sure if you run manual tests once they might be faster than test implementation, but having an automated test suite protects against regression. Having to do a full manual test for every change is going to consume a lot of time.

[ Parent | on HN ]

Re:The Cost of Skipping TDD and Code Reviews (2016) by viach on Monday September 11, 2017 @02:36AM (#15216454)

If your app is more than a todo list, there is no way manual tests are faster than automated tests. Writing software without tests is like running on minefield, you actually can get quite far, probably.

[ Parent | on HN ]