When one of my colleagues left for a new opportunity, I inherited the continuous build setup he built for our project. This has meant spending the past few weeks scrambling to get up to speed on CruiseControl.NET, MSTest and Subversion (among other things). Because we don’t use TFS, creating a build server required us to install Visual Studio 2008 in order to run unit tests as part of the build, along with a number of other third-party tasks to make MSBuild work more like NAnt. So the first time a build failed because of tests that had passed locally, I wasn’t looking forward to figuring out precisely which of these pieces triggered the problem.
After reimplementing unit tests a couple of different ways and still getting the same results (tests passing locally and failing on the build server), we eventually discovered that the problem was a bug in Visual Studio 2008 SP1. Once we installed the hotfix, our unit tests passed on the build server without us having to change them. This hasn’t been the last issue we’ve had with our “TFS-lite” build server.
Build timeouts have proven to be the latest hassle. Instead of the tests passing locally and failing on the build server, they actually passed in both places. But for whatever reason, the test task didn’t really complete and build timed out. Increasing the build timeout didn’t address the issue either. Yesterday, thanks to the Microsoft Build Sidekick editor, we narrowed the problem down to the MSTest task in our build file. The task is the creation of Nati Dobkin, and it made writing the test build target easier (at least until we couldn’t get it to work consistently). So far, I haven’t found (or written) an alternative task, but I did find a blog post that pointed the way to our current solution.
<!– MSTest won’t work if the tests weren’t built in the Debug configuration –>
<Target Name=”Test:MSTest” Condition=” ‘$(Configuration)’ == ‘Debug'”>
<MakeDir Directories=”$(TestResultsDir)” />
<MSBuild.ExtensionPack.FileSystem.Folder TaskAction=”RemoveContent” Path=”$(TestResultsDir)” />
<Exec Command=””$(VS90COMNTOOLS)..IDEmstest.exe” /testcontainer:$(TestDir)<test assembly directory>bin$(Configuration)<test assembly>.dll /testcontainer:$(TestDir)<test assembly directory>bin$(Configuration)<test assembly>.dll /testcontainer:$(TestDir)<test assembly directory>bin$(Configuration)<test assembly>.dll /runconfig:localtestrun.testrunconfig” />
TestDir and TestResultsDir are defined in a property group at the beginning of the MSBuild file. VS90COMNTOOLS is an environment variable created during the install of Visual Studio 2008. Configuration comes from the solution file. Actual test assembly directories and names have been replaced with <test assembly> and <test assembly directory>. The only drawback to the solution so far is that we’ll have to update our MSBuild file if we add a new test assembly.
Why are you using MSTest if you are not using TFS?
I get the impression that the problems you have described are a result of you using MSTest, rather than the absence of TFS.
We’re a Microsoft shop, and using MSTest is just one of a number of technologies we’re trying for the first time on a trial basis. Our other projects tend to use NUnit (which I prefer because it works nicely with ReSharper). Now that we know it’s possible, we’ll see if we try the same thing the next time we have to stand up a build server.
Here is how to dynamically pickup the test assemblies as long as you are consistent with naming…
<!–‘%(Fullpath)’, ‘$(TestContainerPrefix)’)” />–>
Thanks for the tip Daniel, I’ll have to try this very soon.
We use JetBrains TeamCity extensively… 20+ large projects with .NET, Java and ColdFusion. It works great, is cross-platform and can easily run MSTest, NUnit, JUnit or CFUnit…
TFS is a bloated, MS-specific, overpriced piece of xxxx.