“BuildMaster is absolutely swell!” “...this is a very solid piece of software!” “...manual, error-prone deployments are a thing of the past...” “...our confidence in the reliability and repeatability of the deployment process has been restored...” “...we can now react at the speed of business...” “...it's 2:45 AM your time?! Do you guys never sleep?” “BuildMaster made us re-think what proper deployment is...” “...we implemented a *real* deployment process...” “...BuildMaster makes sense of incremental builds and their very liquid feature sets...” “...all of my projects are building wonderfully and are fully integrated into deployment...” “...extremely capable software, especially in an enterprise environment...” “BuildMaster is a great tool for automating the build process, but stands head and shoulders above other tools...” “...the best thing since sliced bread when it comes to managing projects and their environments...”

Running Unit Tests

Units tests play a vital role in Continuous Integration, TDD, and overall software quality. BuildMaster makes it easy to ensure that your tests are run when building to an environment of your choice via a number of supported test runners, including:

To run tests during a deployment, simply add the Testing action of your choice to your deployment plan:

image

For this example, I'll be using NUnit. I'll configure the action with the path to the console test runner and the path of the test project assembly:

image

Once saved, my deployment plan to the Testing environment will display the action:

image

Now, whenever I execute a build to my Testing Environment, the tests will run. The results of the test will be linked to from the Build Execution Details page:

image

If I select [test results], I'll see a summary of all the tests that were run:

image