[Moose-dev] Re: showing a diff on #assert:equals:

On Tue, Dec 1, 2015 at 7:31 AM, Andrei Chis &lt;chisvasileandrei(a)gmail.com > wrote: > > > On Tue, Dec 1, 2015 at 1:05 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com&gt; wrote: > >> Uhhh that's very cool. Quick question, what happens if the textual >> representation of the actual vs expected is the same yet the objects are >> not #= ? >> It shows no diff and then I must go to see the inspector? >> > > These textual representations can be customized per each object type, > however if they are the same now it just shows the diff pane with no > differences. > Another idea would be to also show two inspectors side-by-side apart > from the diff. > A side-by-side inspector would be another really cool addition for when the string comparison won't work. > Then even if you see or not a difference in the textual diff, you > could use the inspector to look at differences between the state. > Also right now the diff is textual. Adding better diff widgets for > specific data types would help. > > Oh yes. But I think that adding a side-by-side inspector would be a great second step in which you know you can always fall back no matter which kind of object.

BTW...since we are near Christmas... it would be terrific to have a button somewhere to show/hide the #setUp method besides the code representing the piece of stack you clicked. Sometimes when I am debugging test failures that had a setup I always have to open another window with the setup because I don't remember everything I did there and that's useful information to understand what a test could have failed. There was a Nautilus plugin for that some time ago.

Cheers, _______________________________________________