I spent a lot of time developing tests for my last project, and I'm really not sure if the ROI was spent on the time spent.
I work as one person and I create web applications. I don’t have to “prove” that my software works for anyone (except my users), and I worry that over the past months I have spent a lot of time reloading the test code.
My question is that I like the idea of TDD for small groups of software developers, how does this help a single person team quickly create high-quality code?
thanks
=> ran into this today, from the blog of joel spolsky, one of the founders of stackoverflow:
http://www.joelonsoftware.com/items/2009/09/23.html
"Zawinski did not do many unit tests. They" sound great in principle. Given the leisurely pace of development, this is certainly the way to go. But when you look at: “We have to go from zero to the end in six weeks, well, I can’t do this if I don’t cut something. And what I’m going to cut is material that is not entirely critical "And unit tests are not critical. If theres no unit test the client is not going to complain about it." "
as I get older, I think I am becoming more aware that this is just speed and functionality. I would like to build unit tests. but since we only have so much time at our disposal, I would rather build it faster and rely on beta testing and good automatic error reporting to filter out any problems as they arise. if the project ultimately gets so big that it bites me **, it will generate enough revenue that I can justify by restructuring.
source
share