It would be good to document this knowledge of what is expected in our test suites. Especially if some are known to fail. Is there a pattern already in use? E.g. Method comment, pragma, wiki page entry? If not what should we adopt?
Thanks mike On 4/1/09, Marcus Denker <[email protected]> wrote: > > On 01.04.2009, at 11:31, Stéphane Ducasse wrote: > >> >> On Apr 1, 2009, at 11:12 AM, Lukas Renggli wrote: >> >>>> lukas is it normal that we get 3 tests yellow - did you get the same >>>> in your image? >>> >>> #testToDoOutsideTemp and #testWhileModificationBefore are broken. I >>> don't think that should stop us from integrating the closures into >>> Pharo. Most "industrial strength" Smalltalk implementations have many >>> more closure bugs than Pharo. >> >> This is integrated already and this is good to have such great test >> suites. >> I will integrate them this evening. >> > > Lukas' teste should be already in, I think. > > Marcus > > > -- > Marcus Denker -- [email protected] > http://www.marcusdenker.de > > > _______________________________________________ > 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
