This post originated from an RSS feed registered with .NET Buzz
by Duncan Mackenzie.
Original Post: Team Chat on Unit Testing coming up next Thursday (3/18)
Feed Title: Code/Tea/Etc...
Feed URL: /msdnerror.htm?aspxerrorpath=/duncanma/rss.aspx
Feed Description: Duncan is the Visual Basic Content Strategist at MSDN, the editor of the Visual Basic Developer Center (http://msdn.microsoft.com/vbasic), and the author of the "Coding 4 Fun" column on MSDN (http://msdn.microsoft.com/vbasic/using/columns/code4fun/default.aspx). While typically Visual Basic focused, his blogs sometimes wanders off of the technical path and into various musing of his troubled mind.
A few team members have blogged about this already, but here I go again...
Unit testing is a method of testing individual software components. Each function in every class is tested to make sure it does its job correctly, with the hope that if everything works correctly by itself, higher level problems will be less common or much easier to debug. Wondering if it is right for you? Already doing it, but looking for best practices? This is your chance to chat with unit-testing experts and enthusiasts from the C# team.
You can find the description, an outlook reminder and a link to the chatroom here: http://msdn.microsoft.com/chats/#vs_mar18 (A few weeks ago I added anchors [as in #vs_mar18] to the chats page to allow folks to link directly to an individual chat... so now I just have to use it whenever possible :) )