Enter custom CruiseControl tasks. As of CruiseControl.NET 1.5, publishers are simply tasks placed in the “publishers” section of the project configuration.

The official CruiseControl.NET documentation explains how to create a custom task. Kris has a very helpful blog post specifically on creating a custom publisher. Neither of them explain how to obtain the unit test results, so that’s what I want to show here.

Unit test results don’t show up in the integration result object passed to the task. To get the unit test results, you have to read them from the build log (luckily, it’s standard xml). Make sure to include a <merge> publisher that includes the NUnit results file in your project configuration before your custom publisher or the test results won’t be there.

public void Run(IIntegrationResult result)
{
    if (result.Status != IntegrationStatus.Unknown)
    {
        string fn = new LogFile(result).Filename;
        string logFileName =
            StringUtil.RemoveInvalidCharactersFromFileName(fn);
        string logFileDir = result.BuildLogDirectory;

        string logFilePath = Path.Combine(logFileDir, logFileName);
        int totalTests;
        int failedTests;
        int testsNotRun;

        using (var fileStream = File.Open(logFilePath,
            FileMode.Open, FileAccess.Read))
        {
            XDocument doc = XDocument.Load(new XmlTextReader(fileStream));

            var testResultsList =
                doc.XPathSelectElements("//build//test-case");
            if (testResultsList != null)
            {
                foreach (var testResults in testResultsList)
                {
                    totalTests++;
                    string execAttr =
                        testResults.Attribute("executed").Value;
                    bool wasRun = bool.Parse(execAttr);

                    if (!wasRun)
                    {
                        notRun++;
                    }
                    else
                    {
                        string succAttr =
                            testResults.Attribute("success").Value;
                        bool succeeded = bool.Parse(succAttr);
                        if (!succeeded)
                        {
                            failedTests++;
                        }
                    }
                }
            }
        }
        // Do something with the results
    }
}

The function StringUtil.RemoveInvalidCharactersFromFileName comes from CruiseControl.Core. A similar method of finding the log file path is used in some of the built in tasks. Once you have the location of the log file, you can easily use xpaths to parse any part of the test results. I wrote some code to filter specific test namespaces into the results so we can report on different sets of tests off of the same build.

If you’re interested in the overall build status, I would use IIntegrationResult.Status rather than LastIntegrationStatus. I believe LastIntegrationStatus actually refers to the previous rather than the current run.