My specific usecase is from a pragmatic TDD perspective - failing test, in the debugger you fix the test and press proceed - expecting green. Getting red, and then immediately running again to get red takes away from our story of love coding and loving your debugger - and even Cassie me to mistrust the tools.
I get the idea that you can jiffy in the debugger and cause a false pass - but I feel you are penalised for doing it right at the moment. Of course these tests will get run again, but I like the idea that if I did it right, it should recognise this, not incur an extra click and moment of doubt. A button to rerun the whole lot, or automatically rerun, or just run it would work for me. Tim Sent from my iPhone > On 10 Nov 2017, at 17:56, Richard Sargent > <richard.sarg...@gemtalksystems.com> wrote: > > That would be fine. > The point is that, without running the test in its entirety, from start to > finish, without interruption, error, or failure, one cannot claim success. > >> On Fri, Nov 10, 2017 at 9:34 AM, Sean P. DeNigris <s...@clipperadams.com> >> wrote: >> Richard Sargent wrote >> > The only reliable conclusion one can make from such an interrupted run is >> > whether it failed again. So, it would be possible to determine that the >> > test should be coloured red, but it is impossible to *reliably* claim that >> > the test should be coloured green. >> >> What if we ran the test again as if from the browser/runner before setting >> the icon? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >
