And just putting it back to gray? As "not run"? On Wed, Nov 15, 2017 at 10:44 AM, Denis Kudriashov <dionisi...@gmail.com> wrote:
> 2017-11-15 1:49 GMT+01:00 Sean P. DeNigris <s...@clipperadams.com>: > >> Ben Coman wrote >> > Or it could go to Amber, half-way between green & red to mean probably >> > correct. >> >> Ha ha. >> >> Again, it seems that just automatically rerunning the test immediately >> after >> a human-manipulated run and setting the color based on that second run >> addresses all points on both sides, no? >> > > Except that sometimes we are debugging slow test and running it second > time automatically after "proceed" can be not appropriate. > We are talking about single test run. If user have any doubts about result > It is his responsibility to rerun the test. User knows what he is doing > when he debug and fix the test. No intelligence is required here. > > And anyway current fix just provides consistent behaviour to debugging > from explicit breakpoint/halt. In that case the result was always in sync > with debug session. > > >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13
