I can completely understand there being disagreement about how to test code, how much testing is enough, when to write test (test driven vs write tests later), etc.
But what boggles my mind is we've got people in this very thread who, if I'm interpreting their comments correctly, are arguing against doing any testing at all! WTF? How, in any non-trivial codebase, are you going to prevent regression?
Does anyone here have any experience in another engineering discipline (civil, mechanical, electrical engineering, etc). Isn't some sort of testing an accepted part of the process?
Maybe I'm wrong, but this seems like a huge sign of the immaturity of the discipline of software development.
I may be reading things wrong, but I think people are arguing against unit testing, which is the focus of TDD.
I hope people aren't arguing against integration testing. I agree with the original post that unit-testing can become onanistic fairly easily, but I think that that is a failure mode for just about any coding style (coding for the sake of coding vs testing for the sake of testing).
But what boggles my mind is we've got people in this very thread who, if I'm interpreting their comments correctly, are arguing against doing any testing at all! WTF? How, in any non-trivial codebase, are you going to prevent regression?
Does anyone here have any experience in another engineering discipline (civil, mechanical, electrical engineering, etc). Isn't some sort of testing an accepted part of the process?
Maybe I'm wrong, but this seems like a huge sign of the immaturity of the discipline of software development.