{"id":636,"date":"2009-01-08T19:13:36","date_gmt":"2009-01-08T18:13:36","guid":{"rendered":"http:\/\/www.navision-blog.de\/2009\/01\/08\/how-i-do-continuous-integration-part-3-running-automated-unittests\/"},"modified":"2009-01-08T19:15:12","modified_gmt":"2009-01-08T18:15:12","slug":"how-i-do-continuous-integration-part-3-running-automated-unittests","status":"publish","type":"post","link":"http:\/\/www.navision-blog.de\/blog\/2009\/01\/08\/how-i-do-continuous-integration-part-3-running-automated-unittests\/","title":{"rendered":"How I do Continuous Integration with my C# \/ F# projects – part III: Running automated UnitTests"},"content":{"rendered":"

In the last two posts I showed how to set up a Subversion (part I: Setting up Source Control<\/a>) and a TeamCity server (part II: Setting up a Continuous Integration Server<\/a>). <\/p>\n

This time I will show how we can integrate NUnit<\/a> to run automated test at each build. TeamCity supports all major Testing Frameworks (including MS Test) but I will concentrate on NUnit here.<\/em><\/p>\n

\n

"NUnit is a unit-testing framework for all .Net languages. Initially ported from JUnit<\/a>, the current production release, version 2.4, is the fifth major release of this xUnit based unit testing tool for Microsoft .NET. It is written entirely in C# and has been completely redesigned to take advantage of many .NET language features, for example custom attributes and other reflection related capabilities. NUnit brings xUnit to all .NET languages."<\/p>\n

[product homepage<\/a>] <\/p>\n<\/blockquote>\n

Creating a TestProject<\/h5>\n

First of all download and install NUnit 2.4.8 (or higher) from http:\/\/www.nunit.org\/.<\/a><\/p>\n

Now we add a small function to our F# source code:<\/p>\n

let rec <\/span>factorial = function  \n  <\/span>| 0 -> <\/span>1\n  | n when <\/span>n > 0 -> <\/span>n * factorial (n-1)\n  | _ -> <\/span>invalid_arg "Argument not valid"<\/span><\/pre>\n
This is the function we want to test. We add a new C# class library to our solution (e.g. \u201cTestCITestLib\u201d \ud83d\ude09 ) and add a reference to nunit.framework<\/em>. Inside this new TestLibrary we add a TestClass with the following code:<\/p>\n
namespace <\/span>TestCITestLib\n{\n    using <\/span>NUnit.Framework;\n\n    [TestFixture<\/span>]\n    public class <\/span>FactorialTest\n    <\/span>{\n        [Test<\/span>]\n        public void <\/span>TestFactorial()\n        {\n            Assert<\/span>.AreEqual(1, Program<\/span>.factorial(0));\n            Assert<\/span>.AreEqual(1, Program<\/span>.factorial(1));\n            Assert<\/span>.AreEqual(120, Program<\/span>.factorial(5));\n        }\n\n        [Test<\/span>]\n        public void <\/span>TestFactorialException()\n        {\n            Program<\/span>.factorial(-1);\n        }\n    }\n}<\/pre>\n
To ensure the build runner is able to compile our solution we put the nunit.framework.dll near to our TestProject and commit our changes.<\/p>\n
\"Adding<\/p>\n
Configure TeamCity for UnitTesting<\/h5>\n
The next step is to tell TeamCity that the build runner should run our UnitTests:<\/p>\n
\"Configure<\/p>\n
If we now run the build we should get the following error:<\/p>\n
\"UnitTest<\/p>\n
Our second test function failed, because we didn\u2019t expect the System.ArgumentException<\/em>. We can fix this issue by adding the corresponding attribute to the Testfunction:<\/p>\n
[Test<\/span>,\n ExpectedException<\/span>(typeof<\/span>(System.ArgumentException<\/span>))]\npublic void <\/span>TestFactorialException()\n{\n    Program<\/span>.factorial(-1);\n}0<\/pre>\n
\"Tests<\/p>\n
Configure the build output<\/h5>\n
At this point we have a minimalistic Continuous Integration infrastructure. Every time someone performs a Commit on our repository a automated build will be started and the sources will be tested against the given UnitTests. Now we should concentrate on getting our build output \u2013 the artifacts. The term artifact is usually used to refer to files or directories produced during a build. Examples of such artifacts are:<\/p>\n
    \n
  • Binaries (*.exe, *.dll) <\/li>\n
  • Software packages and installers (*.zip, *.msi) <\/li>\n
  • Documentation files (e.g. help files) <\/li>\n
  • Reports (test reports, coverage reports, \u2026) <\/li>\n<\/ul>\n
    At this time we are only interested in the binaries (this means CITestLib.dll). We can add the following artifact definition to our TeamCity project:<\/p>\n
    \"Configure<\/p>\n
    If we now rebuild our solution the build runner collects the configured artifacts and stores them with all build information:<\/p>\n
    \"Collected<\/p>\n
    Next time I will show how we can add more artifacts \u2013 e.g. an automated documentation.<\/p>\n","protected":false},"excerpt":{"rendered":"
    In the last two posts I showed how to set up a Subversion (part I: Setting up Source Control) and a TeamCity server (part II: Setting up a Continuous Integration Server). This time I will show how we can integrate NUnit to run automated test at each build. TeamCity supports all major Testing Frameworks (including […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12,23,448,29,3],"tags":[492,664,498,500,219,190,499,458,285,174],"_links":{"self":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/636"}],"collection":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/comments?post=636"}],"version-history":[{"count":1,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/636\/revisions"}],"predecessor-version":[{"id":637,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/636\/revisions\/637"}],"wp:attachment":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/media?parent=636"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/categories?post=636"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/tags?post=636"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}