ok http://code.google.com/p/pharo/issues/list?thanks=1769
On Jan 10, 2010, at 9:40 AM, Lukas Renggli wrote: > Looks like the code of Adrian Lienhard ;-) > > I guess that it tries to fix tests so that they do not pup-up a dialog > when they compile code. > > Initially the code in SUnit was like this: > > TestCase>>runCase > [self setUp. > self performTest] > ensure: [ > self tearDown. > self cleanUpInstanceVariables ] ] > > Then it was change to this (this is where I discovered the issue): > > TestCase>>runCase > Author > useAuthor: 'TestRunner' > during: [ > [self setUp. > self performTest] > ensure: [ > self tearDown. > self cleanUpInstanceVariables ] ] > > In the latest version it was changed again: > > TestCase>>runCase > Author > ifUnknownAuthorUse: 'TestRunner' > during: [ > [self setUp. > self performTest] > ensure: [ > self tearDown. > self cleanUpInstanceVariables ] ] > > In any case the author name is 'TestRunner' if you edit source code > anywhere in the system when a debugger on a test is open. Also I am > not sure what happens if you have multiple debuggers on tests open, > that might give very strange situations. > > I suggest that we revert to the earliest presented version of the > method in question, and fix the particular tests that compile code. > > Lukas > > -- > 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
