Searching and creating specs from Inline Specs List while a test is Running

[sync-by-unito[bot]]

Complex interactions like typing don't work well when a test is actively running in the Runner. A test needs to trigger focus to do many of the things it does, meaning we interrupt typing.

More details in this thread: https://cypressio.slack.com/archives/C02MYBT9Y5S/p1641917556032300

The approach needs to be decided and design needs to be completed. The two main options are:

1. Warn before interacting, that interacting will stop the current spec from running - using a hover/focus state on the area that can't be interacted with. User can choose to stop, or just wait.
2. When the area is interacted with, inform the user that we have stopped the spec because they took X action.

Both might need a bit more definition around the stopped state - paused vs stopped - and the UI for restarting a test. We have buttons in the reporter but it might not be clear that those are to be used for this situation.

┆Issue is synchronized with this Jira Bug by Unito ┆author: Mark Noonan ┆epic: UI/UX Improvements ┆friendlyId: UNIFY-1029 ┆priority: Low ┆sprint: Unification Release Backlog ┆taskType: Bug

[sync-by-unito[bot]]

➤ Chris Baus commented:

Chris Baus There isn’t a decision on this one. Need to follow up

[sync-by-unito[bot]]

➤ Ryan Manuel commented:

Spoke offline with Brian and Ryan. The approach landed on was to pause the tests if the user interacts with the AUT or anything else that might cause issues. Hopefully this can be done using existing APIs. The user can then unpause or rerun the test suite when they are ready to proceed again.

https://cypressio.slack.com/archives/C02560911D0/p1644967006381699 ( https://cypressio.slack.com/archives/C02560911D0/p1644967006381699|smart-card )

[sync-by-unito[bot]]

➤ Chris Baus commented:

Jennifer Shehane We have Highest on this, but there are some thoughts that this happens in 9.x. Maybe we should deprioritize

[sync-by-unito[bot]]

➤ Jennifer Shehane commented:

Chris Baus This may be an issue in the CT tests which was in Alpha and I wouldn’t consider this optimal behavior. This was never an issue in E2E tests as the specs list did not exist inline. This is high priority. It introduces non-determinism in user’s tests when running via cypress open.

[github-actions[bot]]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[cypress-app-bot]

This issue has been closed due to inactivity.