From: Vladimir B. <vla...@bo...> - 2002-02-19 01:36:07
|
Personally a disagree. The problem is not in how JUnit asserts the strings, but how it displays the result. The solution of a 'display' problem must be solved in the UI/textUI and not in the assertions. In 99.999% of the cases, you won't have problems when asserting strings so proposing a solution that will affect everyone (and confuse some) to solve a rare problem is not the thing to do (imho) Another idea is to have a small UI application were you can paste the result of the failure message and have a visual response where your strings differ. This tool can be stand-alone or integrated into the standard UI without too much hassle. But because the stings must first be printed out before you can copy them, you may have to convert the \n \t \r ... in the asserted strings into something more understandable. just an idea -Vladimir -- Vladimir Bossicard www.bossicard.com |