So I have been tasked with implementing unit testing in some legacy code that uses Visual Studio 2005. For various reasons this code base is not ready to be converted to the newest version of .Net. That being said, it is a sizable chunk of code and really needs to be refactored and tested.
There are no unit tests for this codebase. So now is the time to add them. Since we are past the Test Driven Development option we are now going to try Defect Driven Testing. Every time a defect is found or reported, we will write a test that proves it is a defect and then green the test to fix the defect. We will also try to refactor areas around the code in which the defect was found. But before we refactor we will write tests so we are assured not to have changed what the code was doing.
Visual Studio 2005 does not have the MS Testing framework unless you have purchased the "Test" version of Visual Studio. VS 2008 and forward included the testing framework by default. So I downloaded Nunit.
Now I haven't used Nunit since 2008 so I wanted to make sure I had everything working. I tried running the sample tests that were downloaded with the installer. I opened the samples solution and keyed ctrl-shft-b to build the solution. Fail.
I thought, what? This should work out of the box. Well, it didn't. The nunit.framework reference in the project had the little yellow warning triangle because it couldn't find the assembly. So I removed the reverence and added it again. Voila! It compiled. Great, moving on.
Then I added Nunit as an external tool like I remembered I had to do to get a quick link in Visual Studio. So I clicked Tools/External Tools menu and it brought up the External Tools form. I clicked Add to add a new tool and added the path and the name of the tool. Then I forgot what to put in the Arguments and Initial Directory fields so a quick Google search gave me the answer. Or so I thought.
Several links on Google said to set Arguments to $(TargetPath) and Initial Directory to $(TargetDir). This did not work. So what does a guy do who can’t get a software package to work? Look at the documentation, of course!
Well right there in from of my eyes, the Nunit documentation says:
Running From Within Visual Studio
The most convenient way to do this is to set up a custom tool entry specifying the path to NUnit as the command. For a VS2003 C# project, you can use $(TargetPath) for the arguments and $(TargetDir) for the initial directory.
With Visual Studio VS2005 this becomes a bit harder, because that release changed the meaning of the 'Target' macros so they now point to the intermediate 'obj' directories rather than the final output in one of the 'bin' directories. Here are some alternatives that work in both versions:
- $(ProjectDir)$(ProjectFileName) to open the VS Project rather than the assembly. If you use this approach, be sure to rename your config file accordingly and put it in the same directory as the VS project file.
So I did changed the Argument and Initial Directory settings to be $(ProjectDir)$(ProjectFileName) and it all worked!
Interesting how things get remembered. Someone else must have figured this out at my place of employment back in 2008.
Till next time...Technorati Tags: Unit Testing,Visual Studio,NUnit,Tools