Sorry Stef, couldn't resist :) Now there is a distinction between unit tests and the rest of them. Unit tests are depicted as fast and model oriented tests. Later we will have to introduce more kinds of test for enriching our build and development process, tests like functional, architectural, lint, etc.
6942 unit tests run in 34 secs instead than 2:25 min running all tests. I think this will encourage developers to run the tests a little more often. I implemented a fix in the next slice. Name: SLICE-FastAndSlowTestDisociation-JorgeRessia.1 Author: JorgeRessia Time: 16 March 2010, 8:50:41 pm UUID: 9c44289b-bccb-4198-9a98-6dd9979e9bdd Ancestors: Dependencies: Gofer-Tests-JorgeRessia.117, KernelTests-JorgeRessia.164, SUnit-JorgeRessia.86, SUnitGUI-JorgeRessia.45, Tests-JorgeRessia.48 Test cases now answer the message isUnitTest in order to differentiate the unit test from the rest of the tests. - The tests that take too long are no more considered unit tests. - Some test were functional test so there are not considered unit tests. - The TestRunner was modified. A new menu entry can be found in the class pane for selecting all unit tests. Some more fixes here: Name: SLICE-FastAndSlowTestDisociation-JorgeRessia.2 Author: JorgeRessia Time: 16 March 2010, 8:58:11 pm UUID: 86461af2-534b-4091-8f2e-973b650db098 Ancestors: SLICE-FastAndSlowTestDisociation-JorgeRessia.1 Dependencies: Gofer-Tests-JorgeRessia.117, KernelTests-JorgeRessia.164, SUnit-JorgeRessia.87, SUnitGUI-JorgeRessia.45, Tests-JorgeRessia.48 - test fixed Cheers, Jorge On Tue, Mar 16, 2010 at 3:18 PM, Stéphane Ducasse <[email protected]> wrote: > focus on the paper jorge coding only for the fun :) > We have time. > > Stef > > On Mar 16, 2010, at 9:35 AM, Jorge Ressia wrote: > >> Hi, >> >> No, I have to finish that. Is still in my todo list. >> I'll try to make some time today to look into that. >> >> Cheers, >> >> Jorge >> >> On Tue, Mar 16, 2010 at 9:32 AM, Adrian Lienhard <[email protected]> wrote: >>> Yes, it would be very good to have faster tests. In my experience, if tests >>> take too long to run, you don't use them. >>> >>> During the sprint in Lille, Jorge started to sort out long running tests >>> from the rest and make them subclass from SlowTestCase (or something >>> similar). >>> >>> Cheers, >>> Adrian >>> >>> >>> On Mar 16, 2010, at 09:13 , Lukas Renggli wrote: >>> >>>> Btw, I am running the Pharo tests in my builds now too: >>>> >>>> >>>> http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/(root)/ >>>> >>>> Click on duration twice to see the tests sorted by run-time. I feel a >>>> bit bad that the slowest test case is one that I wrote. I'll see if I >>>> can speed that up some more. >>>> >>>> Lukas >>>> >>>> On 15 March 2010 20:56, stephane ducasse <[email protected]> wrote: >>>>> Hi jorge >>>>> >>>>> did you publish the cleans for the tests you did during the sprint? >>>>> >>>>> Thanks Stef >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [email protected] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> >>>> -- >>>> Lukas Renggli >>>> http://www.lukas-renggli.ch >>>> >>>> _______________________________________________ >>>> 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 > > > _______________________________________________ > 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
