nunit-core team mailing list archive

[Nicolas Rivera <730891@xxxxxxxxxxxxxxxxxx>]

It actually works great so far with version 2.5.9.10348.  It is already
helping me -- I have two PCs that stopped at two different tests in the
same test suite, and now I can go back and look at the last portion of
the log to easily analyze if the problem is the production code or the
test.  The only real drawback I have found is that sometimes I have to
kill the GUI process to close it.  But the GUI still repaints and I can
switch between the tabs, which I wasn't sure if I was going to be able
to do.

It sounds from your comments I may have uncovered a bug in the way the
addins work.  If I did, could you please consider Not changing the
current behavior, at least not until you have had time to consider my
feature request?  I really do find this feature helpful for what I am
doing (automated regression tests of whole subsystems including
hardware), and this workaround suits me just as well.

-- 
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/730891

Title:
  GUI runner option to stop upon failure

Status in NUnit Test Framework:
  New

Bug description:
  Feature request.  Add an option to the GUI runner (maybe in Settings)
  to allow the user to specify whether to stop running multiple tests
  upon first failure.  By default the feature would be off.

  This feature would make it easier to debug intermittent failures while
  running integration tests with the GUI runner.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/730891/+subscriptions