Round 1: compile offense, LX defending
- NUnit is a better testing framework than the one supplied by VS2005 (Team Edition for Developers, Testers and the Team Suite)
- I can’t do in VS2005 what he can with NUnit and TestDriven.NET.
Can I defend against the punches to start with. Let’s get ready to ruuuuuummmmmbleeee!!!
1. Reflector integration
Reflector is the must-have tool for every developer, and the new integration from TestDriven.NET is just plain AWESOME!
Aaiii, great first strike, caught me totally off-guard. Has the slapping begun yet?
I’ll have to take this one. VS2005 does no such thing just yet.
1 point for compile
2. Code coverage with NCover or Team Coverage
You got to be kidding. VS2005 has code coverage written all over it. Here we go:
VS2005 can instrument any assembly in your solution, regardless of the language or project type. The assemblies below vary from a regular Class Library, to ItJustWorks compiled C++ application and a website project.
After a testrun you can watch your code and turn on/off the color highlighting on your code coverage.
There is a Code coverage results pane that shows you the details of the code covered. It also allows you to export and import coverage results and to merge one or more of these sets together.
1 point for LX
3. Our new best friend, “Repeat Test Run” 🙂
You mean this:
With automatic selection of the failed test. Rerun original tests will not create a new build of your solution, so you can really rerun the test with the original data (should you happen to need that). Alternatively, you can access the rerun tests from the Test View window:
Notice the selection that allows for an arbitrary set of tests to be run or debugged with the top left button.
The really lucky ones, those that have the Visual Studio Team Edition for Testers, or the filthy rich that own the Visual Studio Team Suite (download it as a 180 day trial version right here. Make sure you order the registered version ahead of time. 😉 can use the Test Manager.
The Test Manager holds a set of test lists where you can group related tests. Even though this solution only has one test project, you could create lists that hold mixes of tests from various projects.
1 point for LX
4. Test with .NET 1.1 from within Visual Studio 2005
Cool trick. Not supported by VS2005. You could install the .NET Framework 1.1 SDK and MSBee (MSBuild Everett Environment) so you can build .NET 1.1 assemblies from VS2005 projects. This only works from the command-line; there is no VS2005 IDE support. I suspect that this “Test with .NET 1.1” option will run the tests using the .NET Runtime 1.1, provided that they are 1.1 compatible, even though it was compiled against the .NET runtime 2.0.
1 point for compile
5. Pluggable unit testing frameworks.
Well, you can run with the VS2005 quality tools testing framework. All the GUI of VS2005 is hard-wired towards that one. Other ones will not be integrated into the testing IDE that VS2005 provides. A pretty irrelevant point, since Dennis wishes to use NUnit and not one of the other testing frameworks.
6. TypeMock.NET integration
Just a irrelevant as point 5. He has not mentioned mocking frameworks as being part of this contest. Too late. This bitslap is about testing frameworks and test integration, not mocking or stubbing frameworks. Sorry, but rules are rules. Standard bitslap rules apply. (And I am making them up as we go along. ).
What’s the score so far? I give it a 2–2 tie. Now, the next post will be my counter-attack. That’s when things get really nasty. VS2005 FTW.