Thanks JB and Vincent, I see why the patch was implemented, due large strings.
I assume that this will only hold true for Strings. I must admit that the line of output expected:<...e> but was:<...> is not all that intuitive at first. Without knowing the previous facts, it seems that it would be nice to have this type of functionality optional. There are many times when I am comparing small strings and would like to see the expected and actual. Anyway now I know how it works, I can be sure to include some logging when I need it. Thank again. "J. B. Rainsberger" <[EMAIL PROTECTED]> on 12/23/2003 05:01:44 PM Please respond to "Cactus Users List" <[EMAIL PROTECTED]> To: Cactus Users List <[EMAIL PROTECTED]> cc: Subject: Re: Odd output with servlet redirector and assert [EMAIL PROTECTED] wrote: > Greetings: > > I am using cactus 1.5/jboss3.0.4/tomcat4.0.6 and trying to using the > most simple config option that I can until I get he hang of writing tests. > > So I have both the client and server side Jars in on the serverside and am > running tests with a browser. > > I noticed the output from assertEquals() does not show the expected and > actual values. > Improper Key: expected:<...e> but was:<...> should be: > Expected: businessrule.customer.invalid.dat > Actual:businessrule.customer.invalid.date Google "JUnit string comparison patch". I think that'll help you. -- 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]
