subject: Enjoy The New Features Of Beta Unit Testing Of Visual Studio 11? [print this page] In recent years, there is some criticism above Unit Testing abilities in the MS Unit Testing outfit. That includes lacking of extensibility attributes, sluggishness, and fewer TDD (Test Driven Development) responsive features.
Some .Net Programmers continue working with the MS-Test because it is element of Visual Studio environment. A few .Net Programmers have stimulated to the Unit Testing frameworks for third-party like xUnit.NET, NUnit, and the MBUnit. A few of the frameworks are lightweight, extensible, and offer tooling support to the Test Driven Developments. Though till now, all the .Net outsourcing tools had smaller integration support in Visual Studio.
In forthcoming VS version, the Microsoft has full some steps for addressing a few of the issues. Some are most determined around tooling support. Because you could imagine, it is ample room in improving MS-Test framework.
Latest Features of Beta Unit Testing VS 2011
Here are some latest features added in the VS 2011 Beta release. However, a few of the features that subject to vary, as well as can even have additional features before RTM release.
Upgrade to VS 2011 from VS 2010
In case, you remember, some few issues are there while upgrading the Unit Test projects to VS 2010 from VS 2008. Just like earlier versions, the projects of VS 2010 Unit Testing will carry on working with the VS 2011. Both are sharing same .Net outsourcing assembly that is Microsoft VS Quality Tools and same runtime.
New Explorer for Unit Testing
Unit Testing Explorer is biggest alteration for MS-Testing tools. Here are some Test Results of Unit Testing VS 2010:
Vs2010-unit-test-error
If you compare above with new VS 2011 Unit Testing Explorer, the new Unit Testing Explorer is seamless, simple, and simple to use. If you experience that the Unit Testing are more associated with the development working than ever before. The Unit Testing View as well as Unit Testing Result windows are removed as well as Unit Testing Explorer offers both tests as well as results in the single window.
Load-default-unit-tests
New searching feature permits you for searching Unit Tests inside Unit Testing Explorer. That also permits you to identify filter criteria like Result: Failed that filter only failing tests. For instance, the Test Groupings, grouped by the assembly name, the class name are missing and expectantly that will be accessible in final release. One can also observe that the Unit Testing timings are presented next to Unit Testing results that instantly provide indication on testing execution time.
Code-coverage
You may also import the accessible code reporting results, export existing results, illustrate highlighted coverage code, etc. You may also have alternative to run code coverage of the entire solution or chosen Unit Tests.
Summary
Since you can see, the VS 2011 is taking a few significant steps towards offering Unit Testing abilities within the MS-Test. It means more and more .Net Programmers are encouraged to write the good Unit Testing as well as follow the best practices like TDD in .Net outsourcing. Optimistically, there can be more developments in MSTest structure itself for superior extensibility.
