Re: Why are Bad Tests Yellow?

I think red is better, as long as there was a useful message about why
it was red.

-Kelly

On Wed, Feb 27, 2008 at 10:24 AM, Charlie Poole
<[email protected]> wrote:
> Hi All,
>
>  Historically, NUnit marks non-runnable tests as yellow in the
>  Gui. This includes methods with args, methods returning a value,
>  abstract methods and classes and classes with no default constructor.
>
>  If we take Yellow to mean "Not Run" this is logical - the test could
>  not be run because it is ill-formed.
>
>  If we take it to mean "Not quite as bad as red" then it doesn't make
>  much sense - obviously, something else was intended and an "error"
>  was made in expressing that intent.
>
>  In NUnitLite, such tests are created in a way that they fail as soon
>  as they are run, with an error message showing why they cannot be run.
>  They show up as red when run from the NUnit gui.
>
>  The "Red" approach makes sense to me. We currently use red to show
>  run-time failures and unexpected exceptions. I think we should also
>  use it to show badly formed tests.
>
>  What do you all think?
>
>  Charlie
>
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  _______________________________________________
>  nunit-developer mailing list
>  [email protected]
>  https://lists.sourceforge.net/lists/listinfo/nunit-developer
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/