Re: Determining if a test passed or failed

Hi Clive,


Thanks for all the very quick responses.  

Charlie, regrading you comment:

I usually don't get into process issues on this list, but the problem as you
describe it seems to indicate a rather serious problem of trust on your
team.
If folks are supposed to be writing tests, are they not doing it? If not,
why not.


I did simplify the situation a bit.  But, rest assured, I do trust the other
programmers.  I am just looking for a safety check: when deadlines are short
and pressure is high, writing a test script for a new 4 line method can end
up filed in the same part of a programmer's mind that governs healthy eating
habits and the ability to iron clothes - never to be dug up again.

Glad to hear it. My day job is as a coach, so this is something I'm
sensitive to. Whatever tool you use, try using an approach
where it is seen as helping the programmers work, rather than as a check on
their work. Sounds like you're on board
with that though.
 
 Tom,
Sounds like you should take a look at NCover
I was hoping to avoid adding yet another tool to mix.  But I will if I have
to.  Still, I am surprised that NUnit does not have the ability to tell
which test is about to run or just ran and whether the test was successful -
it seems like they would be a very useful things to be able to determine for
more than just my case.

Of course, NUnit has that ability, it just does't provide that info to tests
as a matter of separation of concerns. It will happily give out that info to
an extension, which seems to be what you have here - at least in concept.


Which reminds me - I just found this
<http://www.kristofrennen.be/2008/07/19/advanced-setup-and-teardown-with-nun
it/> link describing how to do Assembly level and Namespace level SetUp and
TearDown procedures.  Why isn't this in the NUnit documentation?
 
How about http://nunit.org/?p=setupFixture
<http://nunit.org/?p=setupFixture&r=2.4.7> &r=2.4.7 ? I imagine that's where
Kristof learned of it. :-)
 
Note that you can simply leave the assembly level SetUpFixture outside of
any namespace if you prefer.
 
Charlie

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Nunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nunit-users