Test Case breakpoints

A test that fails three steps in used to mean rerunning the whole thing from the top just to see what happens at step four. Not anymore.

• Set a breakpoint on any step in the Test Case Editor.
• The run pauses there instead of continuing past it, with a countdown before it resumes on its own.
• Resume when you're ready, from the exact step you paused on.
• Edit a step behind an active breakpoint and the run restarts to reflect your change.

Debugging a flaky step stops meaning rerunning the whole case just to get back to the part you actually care about.

#Sprint31