Archives
-
The DuckUnit Extensibility Sample
A little while ago I was working on an example that demonstrates the TestDriven.NET extensibility model. It was an example of how to use the TestDriven.Framework.ITestRunner interface which enables native support for different unit testing engines. This is what NUnit, MbUnit and (soon) Zanebug use allow their test types to executed using TestDriven.NET. The Visual Studio Test Tools (VSTT) support uses a deeper extensibility interface which I'll discuss in a future post.
-
Test With... Application
You may be wondering where the 'Test With... NUnit GUI' option has disappeared to in recent builds. I have been working on opening this up so that other test framework providers can include their GUI test runner as an option. In the current build this menu will be auto populated when TestDriven.NET is activated in the Visual Studio process. This means you won't see these options until TestDriven.NET has been activated on demand (you have used one of TD.NET's other buttons) or 'Startup' is checked in the 'Add-in Manager'. The easiest way to 'fix' this would be to install with the activate on start-up option on by default. I'm reluctant to do this however because I don't want to slow Visual Studio's start-up by even a fraction of a second!