nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

There are two problems here...

1. NUnit is returning a duration of zero for test cases that take less than 1ms to execute.
2. The IDE is categorizing all such tests as 'Not Run' even though the Outcome shows they ran and passed or failed.

We have to fix point 1 in NUnit itself, while the VS guys will have to
fix point 2.

Since NUnit 2.6.2 was just released, we need a workaround in the
adapter. I think I can fix it by arbitrarily setting any duration of
zero to one tick of 100 nanoseconds, so I'll try that.

** Also affects: nunitv2
   Importance: Undecided
       Status: New

** Changed in: nunitv2
       Status: New => Triaged

** Changed in: nunitv2
   Importance: Undecided => High

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

Title:
  Executed fast test appears in Not Run category in Test Explorer

Status in NUnit Test Adapter for Visual Studio:
  In Progress
Status in NUnit V2 Test Framework:
  Triaged

Bug description:
  I use NUnit test adapter in Visual Studio 2012 RTM.

  I group tests in Test Explorer by duration and I see that if test is
  executed in less then 1 ms than it appears in Not Run category. But
  must appear in Fast category.

  For example, when I use built in MSTest test adapter, fast tests
  appear in Fast category and duration column it shows "< 1 ms", so I
  believe this is bug in NUnit test adapter not in Visual Studio.

  I attach screenshots made for test runned with NUnit test adapter and
  MSTest test adapter so you can see the difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-vs-adapter/+bug/1066518/+subscriptions