The community research we published on .NET tools and practices had more than 650 votes leading to some interesting results. We attempt to draw insights.
Pex is a visual studio add-in and unit testing tool developed by Microsoft Research. The tool examines your source code and does a whole lot of job such as suggesting tests and picking values for parameters.
Mighty-Moose, a continuous build and test-runner for .NET, now comes free of charge.
The code coverage utility dotCover 2.0 now includes an integrated unit test runner, rather than requiring ReSharper to run tests. It has been updated to support Visual Studio 2012 RC, and includes new attribute filters.
Navigation is a library that makes ASP.NET Web Forms more testable by moving the CRUD logic out of the codebehind files. Graham Mendick’s article “Unit Testing in the Navigation..” explores some of the features and how unit tests can be written.
Shims are a part of the Microsoft Fakes framework that allow Method interception as a part of testing – including framework methods. This allows for lesser intrusive unit testing, as shown in an article by Rich Czyzewski, “Noninvasive Unit Testing in ASP.NET MVC4 – A Microsoft Fakes Deep Dive”.
SharpDevelop currently comes with support for NUnit and offers the Gallio Addin for MBUnit. Recently Matt Ward announced the addition of MSTest support via a new add-on.
At this week's VS Live conference, Microsoft announced a new Build Service for Team Foundation Service, the Azure-based version of Team Foundation Server. The build service will automatically compile and run unit tests every time files are checked in.
There are several components in an ASP.NET MVC 3 web app – models, controllers, route-handlers, views, html-helpers, client-side code etc. Most of these can be unit-tested, others need integration tests, and several good practices can help you keep your tests more maintainable and avoid making them brittle.
A New Unit Test Explorer, ability to run tests on each build, better Code Coverage tool, support for third party frameworks, a new VS Fakes Framework, better performance and more are all coming together in Visual Studio 11 to provide much better Unit Testing experience for Developers.
NUnit, XUnit.net, QUnit, Jasmine, Chutzpah are all supported in the Visual Studio 11 Beta along with MSUnit, promising better choice and over-all unit-testing experience for developers. And the list is expected to get bigger towards the final release of VS 11.
The latest release of NUnit showcases Action Attributes, a feature which enables the orchestration of test actions across suites, tests, and test cases. Developers can arrange the execution of setup, teardown, and other testing side-effects by applying Action Attributes, which encapsulate test actions, to classes, interfaces, methods, and assemblies within their test projects.
An ongoing problem with specialized platforms is the lack of support for unit testing. Developers are forced to compromise the quality of their tests or their build process in order to get anything working. Recently MonoTouch has made progress in this area, but Windows Phone and Mono for Android still lag behind.
tSQLt is a free, open-source framework for unit testing in SQL Server. By writing tSQLt test cases, developers can create fake tables and views based on production data, then compare expected versus actual results. Tests can be created directly in SQL Server Management Studio.