On Oct 31, 2009, at 6:31 PM, Adrian Lienhard wrote: > If I understand you correctly, the author is permanently set to > 'TestRunner' after running tests?
yes :) > Do you know which tests cause the problem? Reverting to the original > author is done in an ensure block, so I don't see how that can go > wrong right now. Probably if the test raise an error then the handler get confused. Adrian K reported the same problem in the BugTracker Stef > > Adrian > > On Oct 29, 2009, at 20:57 , Stéphane Ducasse wrote: > >> apparently there is a bad interaction between the test runner and the >> author >> because from time to time I get author = TestRunner >> Probably the runner code is not robust enough in case of failure >> capture or something like that. >> >> >> runCase >> Author >> useAuthor: 'TestRunner' >> during: [ >> [self setUp. >> self performTest] >> ensure: [ >> self tearDown. >> self cleanUpInstanceVariables ] ] >> >> _______________________________________________ >> 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
