Removed the loggerFactory... Does not solve my problem :(
It should report a failure and not an error, right? -----Original Message----- From: J. B. Rainsberger [mailto:[EMAIL PROTECTED] Sent: Friday, October 31, 2003 9:20 AM To: Cactus Users List Subject: Re: Every failure leads to an error David Lemieux (QC/EMC) wrote: > Hi everyone, > > I'm juggling with the "failures are anticipated and checked for with assertions > while errors are unanticipated" > > In which circumstances will I encounter a failure? > > I try these three senarios and they report error Remove the LoggerFactory calls and try again. Maybe something is wrong with your logging configuration. By the way: when an assertion fails, JUnit throws an AssertionFailedError, and not an Exception. Read the source code for more information. -- J. B. Rainsberger, Diaspar Software Services http://www.diasparsoftware.com :: +1 416 791-8603 Let's write software that people understand --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
