akuhn/SUnit: run faster tests first & step through tests
Locked
akuhn/SUnit: run faster tests first & step through tests
 
|
Hi Pharo list,
The lastest akuhn/SUnit runs fasters tests first. When running your test suite for the second time, faster tests are run first. For the whole 9000 tests in the dev image, this means that the first 8000 tests are run in like 10 milliseconds. Also I fixed the menues in the test runner, you can now mark either all or single tests are expected defect. If you mark expected defects through the UI they are stored on the class side. The #expectedFailures method on the instance side is still taken into account for compatibility, but storing expected defects on the class side is the preferred way to do it now. I also cleared up the vocabulary. There are no more history on the class side, rather there are two histories one called "last run" and one called "expected defects" that both serve different purposes. The "last run" history is used to mark test results in the browser. The "expected defects" history is used to keep track of expected / unexpected defects. (As far I know, the icons in O2 show this as well.) Plus I added the ability to step through a failed tests. This stops right before the actual test method, rather than at the failed assertion. To step through a failed test, run your tests with the test runner and use the menu of test failures or errors. (OB and O2 might consider adding this option as well. In particular in combination with running fasters tests first a "run and debug/step-through first failure" might be interesting.) To load akuhn/SUnit gofer SystemChangeNotifier uniqueInstance noMoreNotificationsFor: TestCase. Gofer it disablePackageCache; squeaksource: 'akuhn'; package: 'SUnit'; package: 'SUnitGUI'; load. Thank you all for the awesome feedback last time! More is welcome :) --AA _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
Adrian
this sounds really great! I have to check it :) I like the idea that we builder can do a better job at building tools to empower ourselves. Now it is compatible with SUnit ifTrue: [ dear community can you test it and we integrate it :)] > Hi Pharo list, > > The lastest akuhn/SUnit runs fasters tests first. When running your test suite > for the second time, faster tests are run first. For the whole 9000 tests in > the dev image, this means that the first 8000 tests are run in like 10 > milliseconds. cool! I will test it. My problem is that I run tests always in core > Also I fixed the menues in the test runner, you can now mark either all or > single tests are expected defect. If you mark expected defects through the UI > they are stored on the class side. The #expectedFailures method on the > instance side is still taken into account for compatibility, but storing > expected defects on the class side is the preferred way to do it now. > > I also cleared up the vocabulary. There are no more history on the class side, > rather there are two histories one called "last run" and one called "expected > defects" that both serve different purposes. The "last run" history is used to > mark test results in the browser. The "expected defects" history is used to > keep track of expected / unexpected defects. (As far I know, the icons in O2 > show this as well.) > > Plus I added the ability to step through a failed tests. This stops right > before the actual test method, rather than at the failed assertion. To step > through a failed test, run your tests with the test runner and use the menu > of test failures or errors. (OB and O2 might consider adding this option as > well. In particular in combination with running fasters tests first a "run > and debug/step-through first failure" might be interesting.) > > To load akuhn/SUnit gofer > > SystemChangeNotifier uniqueInstance > noMoreNotificationsFor: TestCase. > Gofer it > disablePackageCache; > squeaksource: 'akuhn'; > package: 'SUnit'; > package: 'SUnitGUI'; > load. > > Thank you all for the awesome feedback last time! > More is welcome :) > > --AA > > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
In reply to this post by Adrian Kuhn
in 11138
I got ifUnknownAuthorUse: DNU run | result | result := TestResult new. self on: TestFinished send: #add: to: result. Author ifUnknownAuthorUse: 'TestRunner' during: [TestResource tearDownAll: self resources while: [ self run: self ]]. self unsubscribe: result. ^ result As soon as you fix it I try to run all the test of 11138 _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
Stéphane Ducasse <stephane.ducasse@...> writes:
> in 11138 > I got > ifUnknownAuthorUse: DNU > [...] > As soon as you fix it I try to run all the test of 11138 I won't have time for any fix the next 10 days, deadline madness. For the moment best comment it out yourself. That method is anyway only used as a fall back if no user name is set. It is safe to use SUnit without. --AA _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
In reply to this post by Adrian Kuhn
this loads well in the latest 1,1 core :)
so now we should really have a look and these cool changes Stef On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: > SystemChangeNotifier uniqueInstance > noMoreNotificationsFor: TestCase. > Gofer it > disablePackageCache; > squeaksource: 'akuhn'; > package: 'SUnit'; > package: 'SUnitGUI'; > load. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core.
Niko On Wed, Feb 3, 2010 at 1:13 PM, Stéphane Ducasse <[hidden email]> wrote: > this loads well in the latest 1,1 core :) > so now we should really have a look and these cool changes > > Stef > > On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: > >> SystemChangeNotifier uniqueInstance >> noMoreNotificationsFor: TestCase. >> Gofer it >> disablePackageCache; >> squeaksource: 'akuhn'; >> package: 'SUnit'; >> package: 'SUnitGUI'; >> load. > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683 _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
In reply to this post by Stéphane Ducasse
It was too difficult to integrate.
Stef On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: > What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. > > Niko > > On Wed, Feb 3, 2010 at 1:13 PM, Stéphane Ducasse > <[hidden email]> wrote: >> this loads well in the latest 1,1 core :) >> so now we should really have a look and these cool changes >> >> Stef >> >> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >> >>> SystemChangeNotifier uniqueInstance >>> noMoreNotificationsFor: TestCase. >>> Gofer it >>> disablePackageCache; >>> squeaksource: 'akuhn'; >>> package: 'SUnit'; >>> package: 'SUnitGUI'; >>> load. >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > http://scg.unibe.ch/staff/Schwarz > twitter.com/nes1983 > Tel: +41 076 235 8683 > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
Sad to hear that.
Technical difficulties, or just lack of customers? ^^ --AA On Oct 23, 2010, at 08:05 , Stéphane Ducasse wrote: > It was too difficult to integrate. > > Stef > > On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: > >> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 >> core. >> >> Niko >> >> On Wed, Feb 3, 2010 at 1:13 PM, Stéphane Ducasse >> <[hidden email]> wrote: >>> this loads well in the latest 1,1 core :) >>> so now we should really have a look and these cool changes >>> >>> Stef >>> >>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>> >>>> SystemChangeNotifier uniqueInstance >>>> noMoreNotificationsFor: TestCase. >>>> Gofer it >>>> disablePackageCache; >>>> squeaksource: 'akuhn'; >>>> package: 'SUnit'; >>>> package: 'SUnitGUI'; >>>> load. >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> http://scg.unibe.ch/staff/Schwarz >> twitter.com/nes1983 >> Tel: +41 076 235 8683 >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
In reply to this post by Stéphane Ducasse
Lack of maintainers, too many unwanted features, lack of explanation,
large changes... And this is not that several persons did not look at the code. It got more than the average. Now I'm thinking that with discussion and care we should really get another testing framework with the same API that SUnit because if we want that PharoSunit is the same as Sunit then we are doomed to be backward compatible and no real improvements. Stef On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote: > Sad to hear that. > > Technical difficulties, or just lack of customers? ^^ > > --AA > > On Oct 23, 2010, at 08:05 , Stéphane Ducasse wrote: > >> It was too difficult to integrate. >> >> Stef >> >> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: >> >>> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. >>> >>> Niko >>> >>> On Wed, Feb 3, 2010 at 1:13 PM, Stéphane Ducasse >>> <[hidden email]> wrote: >>>> this loads well in the latest 1,1 core :) >>>> so now we should really have a look and these cool changes >>>> >>>> Stef >>>> >>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>>> >>>>> SystemChangeNotifier uniqueInstance >>>>> noMoreNotificationsFor: TestCase. >>>>> Gofer it >>>>> disablePackageCache; >>>>> squeaksource: 'akuhn'; >>>>> package: 'SUnit'; >>>>> package: 'SUnitGUI'; >>>>> load. >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> http://scg.unibe.ch/staff/Schwarz >>> twitter.com/nes1983 >>> Tel: +41 076 235 8683 >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
Understandable.
+1 for breaking backward compatibility. --AA On Oct 24, 2010, at 00:37 , Stéphane Ducasse wrote: > Lack of maintainers, too many unwanted features, lack of explanation, > large changes... > > And this is not that several persons did not look at the code. It > got more than the average. > > Now I'm thinking that with discussion and care we should really get > another testing framework with the same API that SUnit > because if we want that PharoSunit is the same as Sunit then we are > doomed to be backward compatible and no > real improvements. > > Stef > > On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote: > >> Sad to hear that. >> >> Technical difficulties, or just lack of customers? ^^ >> >> --AA >> >> On Oct 23, 2010, at 08:05 , Stéphane Ducasse wrote: >> >>> It was too difficult to integrate. >>> >>> Stef >>> >>> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: >>> >>>> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 >>>> core. >>>> >>>> Niko >>>> >>>> On Wed, Feb 3, 2010 at 1:13 PM, Stéphane Ducasse >>>> <[hidden email]> wrote: >>>>> this loads well in the latest 1,1 core :) >>>>> so now we should really have a look and these cool changes >>>>> >>>>> Stef >>>>> >>>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>>>> >>>>>> SystemChangeNotifier uniqueInstance >>>>>> noMoreNotificationsFor: TestCase. >>>>>> Gofer it >>>>>> disablePackageCache; >>>>>> squeaksource: 'akuhn'; >>>>>> package: 'SUnit'; >>>>>> package: 'SUnitGUI'; >>>>>> load. >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [hidden email] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>>> >>>> >>>> >>>> >>>> -- >>>> http://scg.unibe.ch/staff/Schwarz >>>> twitter.com/nes1983 >>>> Tel: +41 076 235 8683 >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
In reply to this post by Stéphane Ducasse
Couldn't Adrian be the maintainer? I could step in, too.
I don't really know what you have in mind for a testing framework. We have our own independent and fully compatible fork of SUnit: akuhn/SUnit, which is quite a strong code basis. And on top of that we have Phexample, which has its own name, some extra features and gives a clear point where Pharo is different from the rest. Just a suggestion: Let Adrian maintain akuhn/SUnit, perhaps minus the "should" syntax that you don't like (as in: #(a b c) size should = 3), and make akuhn/SUnit part of Pharo core. The new features (having tests depend on one another, "should" syntax) go into Phexample, and I could maintain that. Cheers, Niko On Sun, Oct 24, 2010 at 8:37 AM, Stéphane Ducasse <[hidden email]> wrote: > Lack of maintainers, too many unwanted features, lack of explanation, > large changes... > > And this is not that several persons did not look at the code. It got more than the average. > > Now I'm thinking that with discussion and care we should really get another testing framework with the same API that SUnit > because if we want that PharoSunit is the same as Sunit then we are doomed to be backward compatible and no > real improvements. > > Stef > > On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote: > >> Sad to hear that. >> >> Technical difficulties, or just lack of customers? ^^ >> >> --AA >> >> On Oct 23, 2010, at 08:05 , Stéphane Ducasse wrote: >> >>> It was too difficult to integrate. >>> >>> Stef >>> >>> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: >>> >>>> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. >>>> >>>> Niko >>>> >>>> On Wed, Feb 3, 2010 at 1:13 PM, Stéphane Ducasse >>>> <[hidden email]> wrote: >>>>> this loads well in the latest 1,1 core :) >>>>> so now we should really have a look and these cool changes >>>>> >>>>> Stef >>>>> >>>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>>>> >>>>>> SystemChangeNotifier uniqueInstance >>>>>> noMoreNotificationsFor: TestCase. >>>>>> Gofer it >>>>>> disablePackageCache; >>>>>> squeaksource: 'akuhn'; >>>>>> package: 'SUnit'; >>>>>> package: 'SUnitGUI'; >>>>>> load. >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [hidden email] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> >>>> -- >>>> http://scg.unibe.ch/staff/Schwarz >>>> twitter.com/nes1983 >>>> Tel: +41 076 235 8683 >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683 _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
In reply to this post by Stéphane Ducasse
On Oct 25, 2010, at 10:12 AM, Niko Schwarz wrote: > Couldn't Adrian be the maintainer? I could step in, too. yes but it means being present and reactive. > I don't really know what you have in mind for a testing framework. We > have our own independent and fully compatible fork of SUnit: > akuhn/SUnit, which is quite a strong code basis. but do we need should, class factory..... > And on top of that we > have Phexample, which has its own > name, some extra features and gives a clear point where Pharo is > different from the rest. This is not the difference that we look for. This is addressing people problems. > Just a suggestion: Let Adrian maintain akuhn/SUnit, perhaps minus the > "should" syntax that you don't like (as in: #(a b c) size should = 3), > and make akuhn/SUnit part of Pharo core. The new features (having tests depend > on one another, "should" syntax) go into Phexample, and I could > maintain that. Why not. If adrian wants. Now first we should have - a better name - clean the code = remove class factory + add comments - make sure that the tools can work with it - move the long execution Sunit extension to it - make sure that the tests are green - integrate/digest latest Sunit feature > > Cheers, > > Niko > > On Sun, Oct 24, 2010 at 8:37 AM, Stéphane Ducasse > <[hidden email]> wrote: >> Lack of maintainers, too many unwanted features, lack of explanation, >> large changes... >> >> And this is not that several persons did not look at the code. It got more than the average. >> >> Now I'm thinking that with discussion and care we should really get another testing framework with the same API that SUnit >> because if we want that PharoSunit is the same as Sunit then we are doomed to be backward compatible and no >> real improvements. >> >> Stef >> >> On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote: >> >>> Sad to hear that. >>> >>> Technical difficulties, or just lack of customers? ^^ >>> >>> --AA >>> >>> On Oct 23, 2010, at 08:05 , Stéphane Ducasse wrote: >>> >>>> It was too difficult to integrate. >>>> >>>> Stef >>>> >>>> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: >>>> >>>>> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. >>>>> >>>>> Niko >>>>> >>>>> On Wed, Feb 3, 2010 at 1:13 PM, Stéphane Ducasse >>>>> <[hidden email]> wrote: >>>>>> this loads well in the latest 1,1 core :) >>>>>> so now we should really have a look and these cool changes >>>>>> >>>>>> Stef >>>>>> >>>>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>>>>> >>>>>>> SystemChangeNotifier uniqueInstance >>>>>>> noMoreNotificationsFor: TestCase. >>>>>>> Gofer it >>>>>>> disablePackageCache; >>>>>>> squeaksource: 'akuhn'; >>>>>>> package: 'SUnit'; >>>>>>> package: 'SUnitGUI'; >>>>>>> load. >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> [hidden email] >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> http://scg.unibe.ch/staff/Schwarz >>>>> twitter.com/nes1983 >>>>> Tel: +41 076 235 8683 >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [hidden email] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > http://scg.unibe.ch/staff/Schwarz > twitter.com/nes1983 > Tel: +41 076 235 8683 > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: akuhn/SUnit: run faster tests first & step through tests
|
|
Thanks to Niko for campaigning me as maintainer :) I do feel very
excited about unit testing in Pharo, however these days I gotta concentrate on my thesis only. Please feel free to reuse whatever is of use to you. My code is there to be cloned and forked :) --AA On Oct 26, 2010, at 12:01 , Stéphane Ducasse wrote: > On Oct 25, 2010, at 10:12 AM, Niko Schwarz wrote: > >> Couldn't Adrian be the maintainer? I could step in, too. > > yes but it means being present and reactive. > >> I don't really know what you have in mind for a testing framework. We >> have our own independent and fully compatible fork of SUnit: >> akuhn/SUnit, which is quite a strong code basis. > > but do we need should, class factory..... > >> And on top of that we >> have Phexample, which has its own >> name, some extra features and gives a clear point where Pharo is >> different from the rest. > > This is not the difference that we look for. This is addressing > people problems. > >> Just a suggestion: Let Adrian maintain akuhn/SUnit, perhaps minus the >> "should" syntax that you don't like (as in: #(a b c) size should = >> 3), >> and make akuhn/SUnit part of Pharo core. The new features (having >> tests depend >> on one another, "should" syntax) go into Phexample, and I could >> maintain that. > > Why not. If adrian wants. > Now first we should have > - a better name > - clean the code = remove class factory + add comments > - make sure that the tools can work with it > - move the long execution Sunit extension to it > - make sure that the tests are green > - integrate/digest latest Sunit feature > > >> >> Cheers, >> >> Niko >> >> On Sun, Oct 24, 2010 at 8:37 AM, Stéphane Ducasse >> <[hidden email]> wrote: >>> Lack of maintainers, too many unwanted features, lack of >>> explanation, >>> large changes... >>> >>> And this is not that several persons did not look at the code. It >>> got more than the average. >>> >>> Now I'm thinking that with discussion and care we should really >>> get another testing framework with the same API that SUnit >>> because if we want that PharoSunit is the same as Sunit then we >>> are doomed to be backward compatible and no >>> real improvements. >>> >>> Stef >>> >>> On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote: >>> >>>> Sad to hear that. >>>> >>>> Technical difficulties, or just lack of customers? ^^ >>>> >>>> --AA >>>> >>>> On Oct 23, 2010, at 08:05 , Stéphane Ducasse wrote: >>>> >>>>> It was too difficult to integrate. >>>>> >>>>> Stef >>>>> >>>>> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: >>>>> >>>>>> What's the status of akuhn/SUnit? I couldn't find his code in >>>>>> 1.2 core. >>>>>> >>>>>> Niko >>>>>> >>>>>> On Wed, Feb 3, 2010 at 1:13 PM, Stéphane Ducasse >>>>>> <[hidden email]> wrote: >>>>>>> this loads well in the latest 1,1 core :) >>>>>>> so now we should really have a look and these cool changes >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>>>>>> >>>>>>>> SystemChangeNotifier uniqueInstance >>>>>>>> noMoreNotificationsFor: TestCase. >>>>>>>> Gofer it >>>>>>>> disablePackageCache; >>>>>>>> squeaksource: 'akuhn'; >>>>>>>> package: 'SUnit'; >>>>>>>> package: 'SUnitGUI'; >>>>>>>> load. >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pharo-project mailing list >>>>>>> [hidden email] >>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://scg.unibe.ch/staff/Schwarz >>>>>> twitter.com/nes1983 >>>>>> Tel: +41 076 235 8683 >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> [hidden email] >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> http://scg.unibe.ch/staff/Schwarz >> twitter.com/nes1983 >> Tel: +41 076 235 8683 >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |