1

Closed

NUnit activity does not use TestTimeout argument.

description

I have to run extensive integration tests within a TFS build using nunit.
I am using the NUnit activity of the TFS build extensions v1.10.4.1 but in the commandline I see in the build log, there is no timeout specified while calling nunit-console.exe althoug I specified it in the InArgument of the activity.
Looking on the assembly using ILSpy I figured that the 'GenerateCommandLineCommands' method does not even use the 'TestTimeout' InArgument.
 
Can that please be fixed soon?
I urgently need that and currently my integration tests are aborted with a ThreadAbortException which leads me to believe that the missing timeout could be the issue here.
 
Thanks a lot!
Closed Aug 12, 2012 at 2:36 PM by GuillaumeRouchon

comments

dwellna wrote Jun 8, 2012 at 2:07 PM

Ok, it's not that urgent any more. I had a look in the nunit documentation.
It is stated there, that if no timeout is specified tests may run for any amount of time.
So, back to investigating my ThreadAbortException.

mikeFourie wrote Aug 5, 2012 at 5:27 PM

Looks like this property is not hooked up
    /// <summary>
    /// Set timeout for each test case in milliseconds
    /// </summary>
    [Browsable(true)]
    [Description("Set timeout for each test case in milliseconds")]
    public InArgument<int> TestTimeout { get; set; }
will try get fixed for next release.

thanks for reporting.

Mike

wrote Aug 12, 2012 at 2:36 PM

Resolved with changeset 78780.