Community
Participate
Working Groups
When an assertEquals for two strings fails, there's a nice little drill down that pops up a "diff dialog". This would be great for Collections. Making this an extension point would also be a good idea.
One trick to get the diff dialog for collections is to externalize them into a string.
True, but I'm sure you agree that ideally the IDE should change, not the 'code under development'.
sure, the issue is that the JUnit's asserts don't know about collections, so making progress on this one depends on JUnit
Well, I haven't looked at how the String behavior works, but even if JUnit changes are required, I'm sure you could get them committed and released. :)
Moving back to the JDT/UI inbox
I'd even suggest extending this if possible, to work for ANY Objects. It would be nice to be able to view the objects as side by side trees (like they show in the debuger local variables view).
Hello All, I have implemented an initial set of features, that are capable to compare complex objects visually regardless used technology. Because the implementation can span far behind Eclipse borders, I created a proposal, that tells about major issues and how to address them. The architectural proposal for the complete solution can be found at http://blog.chocolatejar.eu/contribution/2014/02/27/better-visualization-junit-failures/ The implementation home page can be found at http://blog.chocolatejar.eu/org.eclipse.jdt.ui/ Please let me know what do you think about it and what should I do in order to integrated it into Eclipse. Best regards, Andrej
