Unsure on whether this is a unique use-case of using --no-runner-ui along with cy.pause() but it's ideal in the way I'm wanting to work with Cypress. No logs, more display - but just need a way to resume from the intended pauses.
Ah, yah we did not think about this use case. It's mostly been used as a form for debugging or running headlessly, and not intended mostly as a way to interactively work with tests in open mode.
Current behavior
control
panelDesired behavior
control
panel whency.pause()
is hitTest code to reproduce
N/A
Cypress Version
v13.15.0
Node version
v20.9.0
Operating System
6.11.5-arch1-1
Debug Logs
No response
Other
Unsure on whether this is a unique use-case of using
--no-runner-ui
along withcy.pause()
but it's ideal in the way I'm wanting to work with Cypress. No logs, more display - but just need a way to resume from the intended pauses.