On Thu, Dec 3, 2015 at 10:25 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:

On Thu, Dec 3, 2015 at 6:02 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:

Finally it works :)

Now this is a rather generic extension.

If you want to go one step further you can create an extension that shows more contextual information related to your application.

I think I still have some generic possible feedback after playing with it for some hours that if you can implement that at some point it will be super awesome:

1) I want to use the SUnit debugger EVERY TIME I run tests...even if there is no #assert:equals:. Any error , any #assert:  etc, I do want the SUnit Debugger. Why? Because showing setUp and tearDown for example are interesting even if there is no #assert:equals:

2) Point 1 means that the SUnit debugger must support either displaying or not the current vs expected tabs ?  (or maybe a subclass used for #assert:equals: ?)

3) It would be nice to have a button to hide/show the setUp and tearDown. 

4) Would be nice to automatically show tearDown/setUp IF the implementation is NOT the one of TestCase (empty method) and automatically hide if  it is. 

I'll add them to my todo list. Just I do not have too much time right now.

 

I think that's all for the moment. I am already enjoying it. 

OHH BTW... you said " it will not switch to the SUnit extension automatically (that only works in Pharo 5) ". 

Is there a quick dirty/hack/override/workaround/hardcode I can do to make that work in 4.0?  

Had a second look and hopefully made this work :). You'll need to load GT-Debugger-AndreiChis.251.

With this I also fixed the colors in the black theme so you do not need the hack.

Also you can just call #register now instead of #registerExtraToolOn:

Cheers,

Andrei 

Thanks in advance!!!

 

Cheers,

Andrei

On Thu, Dec 3, 2015 at 8:22 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:

Andrei... you rock!!! It works. I copy paste it here so that others can take advantage too. 

Look also the attached screenshot :)

Doru...you were right..you THINK you don't need a any other tool, until someone comes with a little example as a debugger for test cases...wow... those are moldable tools!!!!

The code I used (with the hack of the override) is this: http://ws.stfx.eu/ME85BCYIPSU8

(of course, I published the code via the playground hahahha)

Thank you!

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

--

Mariano
http://marianopeck.wordpress.com

_______________________________________________
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