nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

We had this feature for a short while. In April 2010, we started
disabling Timeout
whenever the debugger was attached. In September 2010, we removed this
code as part of another fix. I can't tell if the removal was accidental or if it
resolved a problem, so I'll have to experiment.

Note that if we re-enable the fix, *all* timeouts will be stopped, not just the
one for the test you are trying to step into. I may put this to the discussion
list to see what other people think. Naturally, you can always comment out
your timeout when debugging.

Charlie

On Wed, Oct 2, 2013 at 2:43 AM, GreenMoose <juggernaut78@xxxxxxxxx> wrote:
> Test below times out for me (with both 2.6.1 and 2.6.2 it seems) when I
> use "step over" on the sleep statement (NCrunch 1.0.47 test runner)
>
> [TestFixture]
>     public class FooTest
>     {
>         [Test]
>         [Timeout(5000)]
>         public void CanDoSomething()
>         {
>             System.Threading.Thread.Sleep(6000);
>             Assert.Fail("Never reaches this line when debugger is attached.");
>         }
>     }
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/543517
>
> Title:
>   Feature: Ignore Timeout attribute in the debugger
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitv2/+bug/543517/+subscriptions

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/543517

Title:
  Feature: Ignore Timeout attribute in the debugger

Status in NUnit V2 Test Framework:
  Fix Released

Bug description:
  Hi,

  It would be nice, if possible, if NUnit could ignore the Timeout
  attribute if it detects it is running in the debugger.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/543517/+subscriptions