For those interested in unit-testing, the next visual studio release (currently codenamed Orcas) will have support for unit testing built in as Microsoft are moving the existing Visual Studio Team edition functionality, back into the professional version of the product. It's a typical Microsoft move to roll down features into the lower-priced version of the product as the new versions are released ( who wants to make an early bet that they'll end up in visual web developer express 2009 :) ), but what's perhaps more interested is trying to guess what they'll add to the next VSTS/team edition release to justify the price.
I'm a longtime fan of MBUNIT (I even contributed the code for the asp.net 2.0 version of the rollback facility in the latest release, as we needed the capability for a project in work), and knew that the original creator of MBUnit, Jonathan de Halleux, had taken a job with Microsoft, so did a little googling earlier tonight and found this post on his blog discussing pex , a very interesting looking Microsoft research project that could go a long way to removing a lot of the repetitive drudgery of writing comprehensive unit tests - as the article says:
"Pex enables a new development experience in Visual Studio Team System, taking test-driven development to the next level. Pex analyzes .NET applications. From a parameterized unit test, it automatically produces traditional unit tests cases with high code coverage. Moreover, when a generated test fails, Pex can often suggest a bug fix.
Pex performs a systematic program analysis. It records detailed execution traces of existing test cases. Pex learns the program behavior from the execution traces, and a constraint solver produces new test cases with different behavior. The result is a minimal test suite with maximal code coverage. When a test fails, Pex uses detailed dataflow information to determine the root cause and a potential bug fix. "