Linked by Flatland_Spider on Wed 1st Oct 2008 00:05 UTC
Microsoft Yesterday Microsoft started introducing Visual Studio 2010 to Windows developers with a press release and a MSDN website. Introductions to the next Visual Studio also popped up on various technology news sites; InformationWeek, ChannelWeb, Microsoft Watch, BetaNews, and Ars Technica each have brief summary and explaination of the information Microsoft has released so far. Only NetworkWorld digs into the subject by asking various developers to give their impressions of the new Visual Studio.
Thread beginning with comment 332004
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Trying to read the article
by jayson.knight on Wed 1st Oct 2008 05:35 UTC in reply to "Trying to read the article"
jayson.knight
Member since:
2005-07-06

There is also a debugging tool that is meant to capture enough system and application state from the testers to get all the information to reproduce bugs. Eliminating the "No-repro" bugs, in the parlance they just made up. This one might actually be pretty cool, as long as you have enough of a bull shit detector to realize that it probably won't eliminate non-reproducible bugs like they claim.


No automated piece of software will ever capture as much useful information as a good QA department.

Reply Parent Bookmark Score: 1

evangs Member since:
2005-07-07

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.

Reply Parent Bookmark Score: 2

PlatformAgnostic Member since:
2006-01-02

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.

Reply Parent Bookmark Score: 3

jayson.knight Member since:
2005-07-06

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.

Reply Parent Bookmark Score: 1