Feature request : enable diagnostic logging

[Mister Oz]

Hello, I've been trying to enable a good size project to use the NUnit Test Adapter under TFS Build (0.96).

Some of the tests have been hanging on the build machine. I've not been able to see anything useful from the NUnit Test Adapter in the vstest logs that we turned on to try to diagnose the problem. The adapter also appears not to be aware of the timeout information in the .testsettings file passed to vstest so the build agent gets wedged.

There are notes on enabling UTE logging here:

    http://blogs.msdn.com/b/aseemb/archive/2012/03/02/how-to-enable-ute-logs.aspx

Could you consider instrumenting the adapter to report progress, perhaps along the lines of:

using Microsoft.VisualStudio.TestPlatform.ObjectModel;

...

        public void RunStarted(string name, int testCount)
        {
            testLog.SendMessage(TestMessageLevel.Informational, "Run started: "+name);
            if (EqtTrace.IsVerboseEnabled)
            {
                EqtTrace.Verbose("Run started: "+name);
            }
        }

Hopefully this makes sense. I'm not overly familiar with the test adapter APIs, the author of the blog post on UTE logs advised on the EqtTrace API privately.

Thanks
Oz

[Charlie Poole (charlie.poole)]

Moved to https://github.com/nunit/nunit-vs-adapter/issues/10 and marked Won't Fix here.