Linked by Flatland_Spider on Wed 1st Oct 2008 00:05 UTC
Thread beginning with comment 332004
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Trying to read the article
by evangs on Wed 1st Oct 2008 05:54
in reply to "RE: Trying to read the article"
RE[3]: Trying to read the article
by PlatformAgnostic on Wed 1st Oct 2008 07:53
in reply to "RE[2]: Trying to read the article"
I agree... nothing is more useful (for lower layer software,to be sure) than a set of great assertions so that the debug builds of the code test themselves to the greatest extent possible. And of course a set of unit tests to drive the system through at least the mainstream cases.
RE[3]: Trying to read the article
by jayson.knight on Wed 1st Oct 2008 17:40
in reply to "RE[2]: Trying to read the article"
That's true, but such tools can go a long way towards making software more robust. If you take that approach, do you not bother with unit tests? After all, the testing department will catch the bugs anyway.
Unit testing should always be done by the developer IMO. Most software practices follow that rule now.






Member since:
2005-07-06
No automated piece of software will ever capture as much useful information as a good QA department.