nunit-core team mailing list archive

[simon misys <711330@xxxxxxxxxxxxxxxxxx>]

> > (I also noted that the tree parent is also given the failure icon,
> > though I don't know if you consider it unfortunate that its properties
> > window does not give any indication that the cause is due to a
> > NotRunnable child assembly.)

> Yes, we migrate Non-Runnable up the tree because it's pretty severe
> in some other cases - bad constructor for example. In fact, this may be
> a different thing, calling for a different category. I'll consider that.

Sorry if I wasn't clear, I meant that from the parent property you
couldn't tell that the failure was due to a NotRunnable with no
TestFixtures.  It's a minor nit - I mentioned it because you pointed out
you could see in the properties of the test-free assembly that the
status was NotRunnable with no TestFixtures, so you could understand why
there was an issue with the assembly.  I was just pointing out that you
can't see that sort of information (that the reason is NotRunnable with
no TestFixtures) in the parent property, so looking at the parent
properties alone would not lead you to understand why the parent icon
indicates failure (the parent properties says success but no more).

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

Title:
  Test-free assembly given failure icon in tree display

Status in NUnit V2 Test Framework:
  New

Bug description:
  A test-free assembly is shown with the failure icon, ie, an X with red
  background, in the GUI runner tree display, as is its parent(s).

  However, the progress bar is green, as expected (assuming all other
  tests pass).

  Why would we want to include a test-free assembly?  Because we want to
  create a single NUnit project for an existing large solution (40+
  Visual Studio projects) containing all of its assemblies and
  executables.  As we progressively add new tests to our product, we
  want NUnit to automatically pick them up without anyone having to
  remember to make sure the corresponding assembly/executable have been
  added to the NUnit project (and Debug/Release configurations).

  It is off-putting (to say the least) and misleading for NUnit label such test-free assemblies as failures in the tree display.
  It also contradicts what NUnit reports in the rest of the GUI (and when the NUnit project is run with the console runner).

  So, I think NUnit should not show test-free assemblies as failures in
  the tree display.  I think they should count as a success, ie, shown
  with a check with green background.

  Thanks.