BrowseUnit v3 on Squeakmap
daniel at qkss.com
Mon Aug 4 15:17:56 UTC 2003
Thanks Romain, I understand the problem now.
Don't worry about doing anything because of me, I just changed the old test
method names by hand.
Buenos Aires, Argentina
"rrobbes" <rrobbes at etu.info.unicaen.fr> wrote in message
news:20030803175319.21347.qmail at rantanplan.info.unicaen.fr...
> Hi Daniel,
> The reason I changed the generation of the selectors is to allow
> a finer navigation between the tests and the methods.
> The previous version didn't allowed to navigate between the test
> and the method in some cases, whereas this one works better.
> For example if you had (as German said earlier) two methods
> #at: and #at:put:, both would point to the generated method
> testAt. This introduces an ambiguity when you want to go back
> (in the previous version you would always go back to #at: ).
> Moreover I find the new version clearer for keyword messages using
> several arguments (by the way I think that for a better integration
> of the tests in the environment, I should not display their names,
> they should just be near the tested method, as I am trying to do
> with my add-on to whisker. The problem is that it does not work
> really well in 3.6 yet ...).
> Anyways if you are worried by backward compatibility, I'll try to do
> something for it (my "lazy evaluation" of this request did spare me
> this work for a week :-) ).
> Thanks for the feedback,
> Daniel Altman a écrit:
> > Hi Romain, first of all, I am using BrowseUnit and I like a lot, thank
> > Now the question: why did you change the generation of the selectors?
> > I don't like the way it is generating them now, but may be there is a
> > I don't get. For example, let's say I have a method called #Add:
> > Version 2 used to generate the test method #testAdd, but version 3
> > #testAddA1. I think the previous one was clearer and now it is not
> > compatible, as you said.
> > Thanks!
> > ======================================
> > Daniel Altman
> > Buenos Aires, Argentina
> > "rrobbes" <rrobbes at etu.info.unicaen.fr> wrote in message
> > news:20030724142352.16320.qmail at rantanplan.info.unicaen.fr...
> >> Hi all,
> >> I uploaded a new version of BrowseUnit yesterday :
> >> from the readme :
> >> BrowseUnit is a package which improve the integration
> >> of unit tests in developpement. A browser have been oppened
> >> to let you try it out.
> >> It's features are :
> >> - Automatic generation of TestCase for classes.
> >> - Automatic generation of test methods.
> >> - Easy navigation between tests and tested code.
> >> - Improved running of tests, and debugging of failures or errors.
> >> - Modification of the Browser to display BrowseUnit functionalities.
> >> There have been a few changes since v2, mainly :
> >> - Generation of tests methods improved, it now takes into account all
> >> the parameters of the original method.
> >> - Navigation improved for several arguments methods and class-side
> > methods.
> >> - SLint now runs in the background, allowing you to do something when
> >> checking your code.
> >> - Less verbosity : no more yes/no questions where 'yes' was always
> > you
> >> wanted.
> >> Your mouse is happier !
> >> - The browser buttons update more often.
> >> - You're spared a few clicks while you debug assertion failures :-).
> >> - The implementation is better factored : most of the code has been
> >> out
> >> of Browser, letting just the GUI improvements there. That way,
> > is
> >> more
> >> easily adaptable to other browsers (Have you ever heard of
> > ?
> >> :-) ).
> >> Note: as I have made quite a few changes, feedback is welcomed,
> >> especially if they disturb you ... I'm mainly thinking of
> >> the suppression of most of the yes/no questions.
> >> Another thing : since the generation of the selectors have changed,
> >> the navigation is not backward compatible. Yell very loudly if
> >> you want it :-) ...
> >> Romain
More information about the Squeak-dev