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.
You're welcome. Perhaps in JUnit 3.9 or 4.0 it will be configurable, on an as-needed basis or even assertion-by-assertion.
--
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]
