Dirk Olmes, dirk.olme..mx.de, wrote:
>Andrus wrote:
>> Well I was thinking more about adding a 3rd failure state:
>>
>> 1. Error - something that failed unexpectedly (no assertions in the tests)
>> 2. Failure - something that failed in the assertion code
>> 3. "Soft Failure" - a special assertion *for bug tracking only*.
>
>4. Expected Failure - test test case will fail but has an assertion that
>a certain error/exception will occur.
I agree here that an "expected failure" is what Andrus is searching for.
I also agree it's nonintuitive and inverting the intent somewhat, but it
works without modification to the JUnit framework.
I'd like to point out two pieces of code I've written that may assist
with this effort:
1) TestingAppender -- A custom Log4J appender designed to catch warnings
and errors logged from the black box you're testing:
<http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/redshed/TestingAppender/>
2) JAssertTestFailureHandler -- A custom JAssert failure handler which
reports back if any any assertions failed:
<http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/redshed/JAssert/>
.......................................................
Jonathan 'Wolf' Rentzsch jon at redshed dot net
Red Shed Software http://redshed.net (847) 584-7465
PGP: B2AF 1A09 F881 EBDE C9D6 C4D2 C04F A3C0 3EC5 D5F2
"There are 10 types of people:
those who count in binary, and those who don't"
This archive was generated by hypermail 2.0.0 : Mon Dec 23 2002 - 13:53:52 EST