In TFS/VS 11, frameworks other than MS Test are supported, which is cool. Peter Provost mentions them here.
OK, so you start to use this great new feature, queue up a team build and the tests aren’t run.
Assem Bansal has a great article here, so you do that, and no tests are run either. Confusing. The issue is that the 64 bit version is not picking up the reference to the test extension even when it is installed. Hey, it is a beta!
I put the steps in a checklist to make it easier for me to follow.
|1||Log on locally to the build server|
|2||Install the nUnit test runner extension|
|3||Run the download, and the extension will be installed|
|4||Open windows explorer, and navigate to the users folder for the account that you are logged in as|
|Copy all the nUnit assemblies from the nUnit extension (you will have to browse them until you see the four listed below.
They will be in C:Users<UserName>AppDataLocalMicrosoftVisualStudio11.0Extensions<Extension Folder>
|6||Add them to a location in version control
If you are doing a lot of build customisation (you probably will be – eventually 🙂 ), it is best practice to have a team project for the extension assemblies as well as the customised build templates
|7||Add the version control reference to the build controller
Build menu – manage Build Controllers – Properties; Set the Version control path to custom assemblies to the location created in step 6.
|8||Queue the build with a solution containing nUnit tests|
|9||The tests are run, and the data is stored in TFS|
And now the tests are in the build. Awesome.