Placement of "Stop Running" button in UI mode

[gsangiolo]

What would you like?

When stepping through a paused execution in the UI mode (cypress run ...), the "step" button is in the same location as the "stop running" button. When stepping through layers of commands, sometimes the "step" button flips to the "stop" while a command is running/blocked. In cases like this, a careless developer can easily cancel their execution by mistake, and have to start debugging all over again.

Can the placement of these buttons be changed to help prevent these issues?

Why is this needed?

I would like this because often I find myself stepping through a test to debug issues, but accidentally click the "stop running" button, and then I need to start my hunt all over again. This feels like a relatively small change for a fairly decent UX improvement

Other

No response

[jennifer-shehane]

@gsangiolo Thanks for the feedback, definitely understand the frustration here.

Our design team has a proposal for a fix noted below:

Current Design

Proposed Design

Disable the 'Next' button when we have previously 'paused' (due to cy.pause, cy.debug) and are now running until the next breakpoint is hit.