Archives
-
NCover on Visual Studio .NET 2002/2003?
Matt Ellis wrote:
-
Test With... Coverage
Last week I announced that TestDriven.NET now has code coverage integration for users of Visual Studio 2005 Team Suite, Developer or Tester. This week I'm happy to announce a solution for all other Visual Studio users! I've now added support for the popular code coverage tool NCover. Peter Waldschmidt the author of NCover has been working with me in order to get the two applications playing nicely together.
-
TestDriven.NET Users Group
I've created a new Google Group for TestDriven.NET Users. You can subscribe to it using email, rss or the web. If you have a question that others would benefit seeing the answer to - please ask it here. If you have any hints and tips for using TestDriven.NET, please contribute them here! I hope this will be the start of a more active user community. I look forward to seeing your posts...
-
TestDriven.NET + Visual Studio Test Tools
TestDriven.NET 2.0 Beta includes support for the Visual Studio Test Tools (VSTT) unit testing framework that comes with Visual Studio 2005 Team Suite, Developer and Tester. If you are using this unit testing framework you will probably find TestDriven.NET a faster and more convenient way to execute your unit tests (if you're not convinced, I recommend you read Brian Button's article). As well as being able to execute your unit tests using TestDriven.NET, you can also view them using the NUnit GUI (when launched from the 'Solution Explorer' context menu). This is achieved using a special adaptor that knows how to handle a subset of the VSTT attributes and functionality.
-
TestDriven Macros for Keyboard Junkies
I've had a number of people email asking where the run all tests in solution command has gone. This command disappeared when I did some refactoring to unify the various 'Run Test(s)' commands. I actually did this to make TestDriven.NET more keyboard friendly. The idea was to make the 'Run Test(s)' command do the right thing depending on context. For example if the code window isn't active, it will execute tests in the highlighted 'Solution Explorer' item. For example if the 'Output' window is active, it will execute tests in the currently active source file. This only works if the 'Track Active Item in Solution Explorer' option is checked (I believe this is no longer the default setting in Visual Studio 2005).
-
Official NUnit Release
I have just uploaded a version of TestDriven.NET that was built against the latest official NUnit release (2.2.6). From now on I'll only be using official NUnit releases rather than doing continuous integration using the latest NUnit source in CVS. There was some method to my madness when I started doing continuous integration with the NUnit source. However now the NUnit feature I needed is part of the official release, there is no longer an imperative to stay on the bleeding edge. This should make for more stable releases and fewer surprises for Charlie Poole and the NUnit team.
-
Got it Covered?
I have recently added a feature that allows the code coverage support built into Visual Studio 2005 Team Suite, Developer or Tester to be accessed using TestDriven.NET. Simply use the new 'Test With... Coverage' button you will find on most of TestDriven.NET's context menus. This will execute a subset of your unit tests with code coverage enabled. You can use it with NUnit, VSTT (Visual Studio Team Test), MbUnit, Ad-Hoc or any other supported test type.
-
Performance Improvements
If you have a test assembly with a lot of unit tests, you should see some pretty dramatic performance improvements with the latest build. I have to thank Grant Drake, from some excellent feedback and repros.