On Tue, Dec 1, 2015 at 1:05 AM, Mariano Martinez Peck <marianopeck@gmail.com> 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. 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. 

Cheers,
Andrei
 

On Mon, Nov 30, 2015 at 8:58 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
Hi,

I updated GTDebugger to automatically show a diff in the debugger when an #assert:equals: fails.

For example if you execute '(GTSUnitExampleFailingTest selector: #testMultiValuedStreaming) debug.' you get the debugger below. Also works when running tests from Nautilus/TestRunner.
The context from where  #assert:equals: was called is also automatically selected.

Inline image 1


Let me know if you run into any issues.

Cheers,
Andrei

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev




--

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev