2010/6/21 Mariano Martinez Peck <[email protected]> > > > 2010/6/17 laurent laffont <[email protected]> > >> Hi, >> >> Autotest is a live testing tool (similar too Ruby Autotest, but the >> Smalltalk way, more dynamic). >> >> Autotest automatically runs tests related to the methods you edit. >> Screencast to see it in action: >> http://lolgzs.free.fr/pharo/autotest3.mpeg >> >> > Hi Laurent. I have just test it and I really like it. I wasn't aware at all > what a Autotest was (I don't know Ruby). >
Cool ! Personnally I really like Ruby Autotest and I use a similar script for PHP. I can't do TDD without it :) > Autotest uses the following heuritics to find the tests to run: >> - if the method is a test, runs it >> - it the method is a test setUp or tearDown, run all the tests of the >> TestCase >> - else find all senders which are tests in the same package and runs >> them (it detects different packages that are related, for example >> ProfStef-Core and ProfStef-Test) >> >> > maybe a new feature: when modifying a TestResource, run all the tests that > references it ? > Good idea. > what happens with subclasses? suppose I refactor/modify a subclass, do you > also run the tests of the superclasses? > Now there's no heuristics on the class level, only method / package. So as long as there's a sender of the method you edit, tests will run. You can have a look at AutotestFinder, heuristics protocol. > > >> To activate the Autotest dashboard >> >> > - open the settings browser >> - go under System >> - check "Show Autotest Dashboard" option >> >> > Here I am confused. This setting, just enables de dashborad or the run of > the tests? I guess one thing is to run the tests and another one is to see > them in the dashborad. > > I would love to be able to enable/disable AutoTest completly. > Closing the dashboard disables Autotest completly. AutotestDashboard sets up as a view of its Autotest instance. When you close it garbageCollect to be sure Autotest>>release is called. > In addition, I think we can add AutoTest to PharoDev 1.2 images. What you > and others think? > I would like more feedback. If you use it you notice that your workflow changes because of that instant feedback. I'm looking for people who use it on real TDD for real projects (as I'm only pharoing on my freetime). I think it can be a great tool we cannot have in «standard» programming languages. Cheers, Laurent > > >> To load it: >> >> Gofer new >> squeaksource: 'Autotest'; >> package: 'Autotest'; >> load >> >> HelpSystem book included. >> >> >> I would like to know what needs enhancements, what to add (and to remove >> :) and whether you would use it or not (and why). >> >> Thanks for feedback. >> >> Cheers, >> >> Laurent Laffont >> >> http://pharocasts.blogspot.com/ >> http://magaloma.blogspot.com/ >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
