Did you mean to send this to the nunit-dev list ?
Merrill Cornish wrote:
Someone sent me mail with a proposal for the use of read, yellow, and green status indications--but I mananged to delete it before saving the return address. [Sorry about that.]
The overall problem we have is that we have three colors but at least five states to distinguish.
* Red means that at least one test ran, ran correctly (e.g., no setup problems), but it found and reported and error it was designed to find while running. This is apparently the only one everyone agrees on. :-)
* Green means that either all tests -or- all all un-suppressed tests (i.e., no Explicit, Ignore, excluded category, or Assert.Ignore()) ran correctly and found no none of the errors they were designed to find.
* Yellow means that either there were some suppressed tests that did not run because they were deliberately suppressed -or- at least one test that WAS supposed to run failed for some reason other than finding an error it was designed to find (e.g., mal-formed source, missing NUnit attributes, error in setup, etc.).
The red tests require looking into. The yellow tests that were supposed to run by didn't need looking into; but the yellow tests that were deliberately suppressed merely need to be remembered. No immediate action is necessarily required for them.
When you look at all of this, the thing that seems to be mucking up the intutive meaning of the red/yellow/green stoplight colors are those tests that were deliberately suppressed. Yes, they need to be remembered, but do they really need to confuse everything else in the process?
I would propose using a status dot of a different color (blue?) to highlight individual tests that did not run because they were deliberately suppressed. These blue status dots do NOT propagate to ancestor nodes in the test tree and they do NOT effect the main status bar.
Just to be certain a blue status dot doesn't get overlooked in a large test set, there could be a blue box that appears some place that will not be hidden by collaping the test hierarchy. (The status row at the bottom, perhaps?)
If we have the "tests that weren't supposed to run anyhow" out of the way, then we are left with simple red/yellow/green status dots and progress bar:
* Red: at least one test ran normally, but found a failure it was designed to fine while running.
* Green: All tests that were supposed to run ran normally, but none found any of the failures they were designed to find.
* Yellow: At least one test that was supposed to run, failed to start or failed to execute properly, but not for any failure it was designed to find.
To make a long story short (too late!), move indications about tests that were not SUPPOSED to be run in the first place out of the standard red/yellow/green hierarchy.
Merrill
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
--
Ian MacLean, Developer, ActiveState, a division of Sophos
http://www.ActiveState.com
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
