Hi Laurent,
I have been playing with the Autotest tool and it's quite cool!
One major enhancement suggestion.
Let's say we have a test method defined as such:
testWhatever
^self somethingElse or: [self testSomethingDifferent].
Removing the method #somethingElse or #testSomethingDifferent from the system
won't trigger the listener to run the test #testWhatever since you only check
for new methods and modified methods.
But what happens if we remove a method (called from a test method) and that
would break the test? I think this should be handled as well.
Besides, another suggestion, why wouldn't we queue the modified methods events
instead of ignoring them when the current process is still running a test and
has not yet completed?
I also suggest that logging should include the test result (not only time &
method name).
Finally, thanks for such a great tool!
-----------------
Benoit St-Jean
A standpoint is an intellectual horizon of radius zero.
(Albert Einstein)
_________________________________________________________________
Look 'em in the eye: FREE Messenger video chat
http://go.microsoft.com/?linkid=9734386_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
