Three CodeRush Unit Test Runner improvements
The CodeRush Unit Test Runner has several improvements in the upcoming major update.
The CodeRush Unit Test Runner has several improvements in the upcoming major update.
The Categories support has been already introduced for the Unit Test Runnerin the current CodeRush release. Now, there are two useful actions added for creating specific keyboard shortcuts to run or debug test cases in the specific category:
See other actions and shortcuts for the CodeRush Unit Test Runner.
—– Products: CodeRush Pro Versions: 12.1 and up VS IDEs: 2008 and up Updated: Apr/09/2012 ID: U010Starting with the next minor update v2011 vol2.8, the Unit Test Runner supports injection of environment variables for 3rd-party tools. Third-party tools may require providing the CodeRush Unit Test Runner with some environment variables for proper execution when launching the Test Runner process.
The CodeRush Unit Test Runner supports running tests from the Silverlight Unit Test Framework which is a part of Silverlight Toolkit now, so it’s easy to test your Silverlight applications.
Once you install the Silverlight Unit Test Framework, you are able to create the Silverlight Unit Test Application project. Here is what the Add Project dialog looks with the Silverlight tab highlighted:
Let’s compare the benefit of the CodeRush Unit Testing Service against the native Visual Studio unit testing support as an example. The first things that may catch your attention are test icons near test methods, test fixtures and namespaces containing test cases:
The Unit Testing Technology shipped in CodeRush Pro allows you to manage, navigate, run, and debug unit test cases of different unit testing frameworks. The technology consists of several parts:
The CodeRush Unit Test Service supports the running and debugging of testing scenarios of the Mashine.Specifications (mspec) framework.
Read more…
CodeRush Unit Test Runner has a set of predefined shortcuts useful for running and debugging unit test cases inside Visual Studio. All shortcuts are easy to remember: they start from a general Ctrl+T keystroke (where T means Testing) followed by a second key which specifies the operation, for example: