![\"clip_image002\"](\"\/\/fluentbytes.azurewebsites.net\/wp-content\/uploads\/2015\/08\/clip_image002.jpg\" "\\"clip_image002\\"")
<\/a><\/p>\nNext we need to get the XUnit Tools so we can start writing tests. For this you go to the Nuget Package manager for the project and there you select the following packages:<\/p>\n
The Project.json file contains besides a set of dependencies also the option to define commands you want to run in the DNX environment. What we are going to do is specify a command called \u201ctest\u201d and we specify we want the XUnit DNX runner to be used for that command. Since we need the test results to be captured in an XML file so we can upload them to TFS as part of the build we specify additional options at the command to output results to an xml file with the \u2013xml option and provide it a file name of the results file. The Project.json file looks then as follows (the blue underline shows the test command:<\/p>\n I won\u2019t go into details about writing XUnit tests, you can read a lot more about this here (http:\/\/xunit.github.io\/docs\/getting-started.html<\/a>) . For now I will show you the code for the class that I called \u201cSomeTests\u201d that contains two tests.<\/p>\n Since we installed the DNX runner using NuGet, after a build the visual studio environment should now show your tests in the test runner automatically after you compile the project.<\/p>\n So everything now runs in visual studio, question remains can we also do things from the command line? To verify this you can start a command prompt at the current solution and then try to run the command<\/p>\n dnx .\\src\\classlibrary1 test<\/p>\n This will probably result in the error that the command dnx is not recognized. This has to do with the fact that we first need to select the right dnx run environment and you can do so with the command line:<\/p>\n dnvm setup<\/p>\n This will setup the dot net environment and make it part of your current path. Now we need to select a dot net framework we want to run on. Since we want the ability to run on non windows environments you can then select the \u201ccore clr\u201d runtime. You can first list all the runtimes available with the command line:<\/p>\n dnvm list<\/p>\n This shows a list like here below:<\/p>\n Active Version Runtime Architecture Location Alias<\/span><\/p>\n —— ——- ——- ———— ——– —–<\/span><\/p>\n 1.0.0-beta5 clr x64 C:\\Users\\vries\\.dnx\\runtimes<\/span><\/p>\n 1.0.0-beta5 clr x86 C:\\Users\\vries\\.dnx\\runtimes<\/span><\/p>\n 1.0.0-beta5 coreclr x64 C:\\Users\\vries\\.dnx\\runtimes<\/span><\/p>\n 1.0.0-beta5 coreclr x86 C:\\Users\\vries\\.dnx\\runtimes<\/span><\/p>\n Next I select the runtime I want to use by using the command:<\/p>\n dnvm use 1.0.0-beta5 \u2013architecture x86 \u2013runtime coreclr<\/span><\/p>\n Now we have set up the runtime environment and now you can type the command:<\/p>\n dnx .\\src\\classlibrary1 test<\/span><\/p>\n and now you will see the test results shown at the console:<\/p>\n xUnit.net DNX Runner (32-bit DNXCore 5.0)<\/span><\/p>\n Discovering: ClassLibrary4<\/span><\/p>\n Discovered: ClassLibrary4<\/span><\/p>\n Starting: ClassLibrary4<\/span><\/p>\n Finished: ClassLibrary4<\/span><\/p>\n === TEST EXECUTION SUMMARY ===<\/span><\/p>\n ClassLibrary4 Total: 2, Errors: 0, Failed: 0, Skipped: 0, Time: 0.106s<\/span><\/p>\n You will now also find an xml file that contains the test results if you look in the location where you executed the command. The result file now contains the test results in the XUnit test format. This format is at the moment not recognized by TFS, they do support MS Test trx format and NUnit out of the box. So we need to do some additional work to make the results usable by TFS build.<\/p>\n Before we can build anything on the server we need to commit our changes locally in our GIT repository and push our changes to the TFS server in a team project that has GIT as version control selected. (you can also work with Team Foundation Server Version control, but since we work cross platform and GIT is available on any platform without MS tools I selected GIT. You could also use Team explorer Everywhere to run from Unix, mac or Linux systems)<\/p>\n In my example here I use Visual studio Online, but this will also work with a on premise server that has TFS 2015 installed. (2015 contains the new Build features I am using here)<\/p>\n When at the TFS web page for build we create a new build definition and call it \u201cASP.NET VNext with XUnit\u201d. Next we start with a build template that has the basic compile things in there.<\/p>\n Next we add a new build step of type PowerShell script so we can set up the DNX environment like we just did, but now on the build server.<\/p>\n Move this step to the top of the build, so it becomes the first step<\/p>\n Next we need to add a script to our project to install the dnvm tools and then select the right dnx environment for the compilation of the project to work. If we don\u2019t do this you will get the error message in the compile step: You can copy the PowerShell script from the following MSDN page that describes this first step:<\/p>\n https:\/\/msdn.microsoft.com\/en-us\/Library\/vs\/alm\/Build\/azure\/deploy-aspnet5<\/a><\/p>\n or just copy the contents here:<\/p>\n I called the script Install_DNX.ps1 and I added it to the solution items folder in my solution<\/p>\n Now you can select this file in the PowerShell step as follows:<\/p>\n When we have this setup, we can now setup the unit testing part. Since the Visual Studio Test step requires an visual studio runner plugin that runs on the full .net framework, I wanted to ensure my tests run clean and also can be run on a build host that I run on a Linux system, so I don\u2019t want to rely on MSTest with an MSTest adapter specified. So I deleted the Visual Studio Test step and replaced it by a PowerShell script that does exactly what we have done in the local run from the command line. So the script for that looks as follows:<\/p>\n Set-ExecutionPolicy unrestricted -Scope CurrentUser -Force<\/p>\n dnvm setup<\/p>\n dnvm use 1.0.0-beta5<\/p>\n dnx $PSScriptRoot\\src\\ClassLibrary4 test.\\nxslt2.exe $PSScriptRoot\\testresults.xml .\\NunitXslt.xslt -o testresultstransformed.xml<\/p>\n Now note the last step of the script. What I did here is leverage a Xslt transformation to change the Xunit format that is currently not recognized by the TFS build an change it to a format it understands Nunit. For this I added an executable called nxslt2.exe that Scott Hanselman described on his blog (http:\/\/www.hanselman.com\/blog\/XSLTWithPowershell.aspx<\/a>) to do simple transformations using PowerShell. I just added the executable also to my solution items folder. The Xslt file I pulled from the github repository of Xunit. In their runners they normally support Nunit as an output format, but this is not supported yet in the dnx runner at the moment. You can find the xslt file here: https:\/\/github.com\/xunit\/xunit\/blob\/master\/src\/xunit.console\/NUnitXml.xslt<\/a><\/p>\n I also added this file to my solution items folder, so I have everything in one place. The output of the transformation is now the file called testresultstransformed.xml and that is the file we are going to upload to the TFS server.<\/p>\n I gave the script file the name RunDnxTest.ps1 and placed it in the Solution Items folder. Here you can see the screenshot of my solutions Items folder in my project that includes the Xslt file, the nxslt2.exe file and the PowerShell script:<\/p>\n One final thing to note is that the script assumes a directory from which it runs. You can specify this in the PowerShell task and I specified it will be the solution root of my project when it is pulled from the GIT repo:<\/p>\n And after adding the script to the solution items folder in my solution and pushing it to the remote repo, you can select it as the PowerShell build step to run the tests.<\/p>\n Ensure that for the PowerShell task you check the option Continue on Error, since when one of the tests fails otherwise your build will be flagged as failed and no results will be uploaded to the server which is the next task.<\/p>\n The final thing we want to add is the task to upload the results file after a test is completed.<\/p>\n When we configure this task we need to select which output result we want to use. Here we select NUnit, since that is the format we transformed the output to in the final step of our PowerShell script that runs the tests. We select the transformed results file and then we are done.<\/p>\n Now we can queue a build on one of our hosted build machines or on your on premise deployed agent.<\/p>\n In my case I selected my own build server that runs in an Azure virtual machine:<\/p>\n And after running the build you can now see the test results uploaded to the TFS server:<\/p>\n<\/a><\/p>\nEnsure your Project.json file contains a test command<\/h4>\n
<\/a><\/p>\nWrite a XUnit test<\/h2>\n
<\/a><\/p>\nRunning the test local<\/h2>\n
<\/a><\/p>\nBuilding the project using TFS build 2015<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n
\nError : The Dnx Runtime package needs to be installed. See output window for more details.<\/strong><\/p>\n# bootstrap DNVM into this session. \n&{$Branch='dev';iex ((new-object net.webclient).DownloadString('https:\/\/raw.githubusercontent.com\/aspnet\/Home\/dev\/dnvminstall.ps1'))}\n# load up the global.json so we can find the DNX version\n$globalJson = Get-Content -Path $PSScriptRoot\\global.json -Raw -ErrorAction Ignore | ConvertFrom-Json -ErrorAction Ignore\nif($globalJson)\n{\n\u00a0\u00a0\u00a0 $dnxVersion = $globalJson.sdk.version\n}\nelse\n{\n\u00a0 Write-Warning \n\"Unable to locate global.json to determine using 'latest'\"\n\u00a0\u00a0\u00a0 $dnxVersion = \"latest\"\n}\n# install DNX\n# only installs the default (x86, clr) runtime of the framework.\n# If you need additional architectures or runtimes you should add additional calls\n# ex: & $env:USERPROFILE\\.dnx\\bin\\dnvm install $dnxVersion -r coreclr\n& $env:USERPROFILE\\.dnx\\bin\\dnvm install $dnxVersion -Persistent # run DNU restore on all project.json files in the src folder \n# including 2>1 to redirect stderr to stdout for badly \n# behaved tools \nGet-ChildItem -Path $PSScriptRoot\\src -Filter project.json -Recurse | ForEach-Object { & dnu restore $_.FullName 2>1 }<\/pre>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n