Re:Unit testing is not (generally) useful
by pmarsh on Thursday February 05, 2009 @11:05AM
(#468061)
It all depends on how your development works.
Let's look at a scenario where you are using an outside framework.
Not writing tests for your code? Framework v2.0 comes out and you want to use a great new feature in that version. Will your app work if you upgrade? Sure you'll have to test/QA your app regardless, but with tests you might have a better idea of where to look for problems.
This is what I'm facing at the moment as a single developer. The app has no test coverage so updating is a laborious process of testing everything by hand.
But getting into testing has it's own problems. The biggest I have with testing is when I read discussions about bugs within the test framework. How much time will you spend working around bugs in the testing framework?
Let's look at a scenario where you are using an outside framework.
Not writing tests for your code? Framework v2.0 comes out and you want to use a great new feature in that version. Will your app work if you upgrade? Sure you'll have to test/QA your app regardless, but with tests you might have a better idea of where to look for problems.
This is what I'm facing at the moment as a single developer. The app has no test coverage so updating is a laborious process of testing everything by hand.
But getting into testing has it's own problems. The biggest I have with testing is when I read discussions about bugs within the test framework. How much time will you spend working around bugs in the testing framework?