Wow. I naively assumed that the entire run-time context was still there as long as the red/yellow test was not garbage collected. Rerunning is obviously the smart thing to do, but snafus non-deterministic tests. So you should just click on those yellow tests over and over till the debugger pops up? ;-) - on On Apr 11, 2009, at 23:15, Lukas Renggli wrote:
indeed but when this is yellow we should be able to click on it?
Clicking on a yellow or red test just re-runs that test. If the test then suddenly passes, you are out of luck.
The problem could be solved by capturing and storing a continuation when a test fails. Like this a debugger could be opened on the original stack that caused the error. This however would require a major rewrite of SUnit, as extra care has to be take when and how to release resources.
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project