chore: add browser state action for debug (#26763)

[dkasper-was-taken]

• Closes Add logic to change browser state #26763

Additional details

Steps to test

• Open a project with associated Cloud Runs, note run not currently active
• Navigate to a non-debug route (Specs, Runs, Settings, etc)
• Open GraphiQL, add entries below

mutation SpecsListHeader_ShowDebugForCloudRun($runNumber: Int!) {
  showDebugForCloudRun(runNumber: $runNumber) { machineId }
}
...
{
  "runNumber": <your above noted cloud run number>
}

How has the user experience changed?

No UX changes associated with the action only

PR Tasks

• Have tests been added/updated?
• [n/a ] Has a PR for user-facing changes been opened in cypress-documentation?
• [ n/a] Have API changes been updated in the type definitions?

[cypress]

31 flaky tests on run #46982 ↗︎

0

27304

1308

0

31

Details:

Revert route change, update spec description
Project: cypress	Commit: 8c6d0e8900
Status: Passed	Duration: 20:54 💡
Started: Jun 2, 2023 6:58 PM	Ended: Jun 2, 2023 7:19 PM

  commands/net_stubbing.cy.ts • 1 flaky test • 5x-driver-electron

View Output Video

Test		Artifacts
network stubbing > intercepting request > can delay and throttle a StaticResponse		Output Video

  cypress/cypress.cy.js • 3 flaky tests • 5x-driver-electron

View Output Video

Test		Artifacts
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video

  create-from-component.cy.ts • 2 flaky tests • app-e2e

View Output Video

Test		Artifacts
... > runs generated spec		Output Screenshots Video
... > runs generated spec		Output Screenshots Video

  specs_list_latest_runs.cy.ts • 1 flaky test • app-e2e

View Output Video

Test		Artifacts
App/Cloud Integration - Latest runs and Average duration > when no runs are recorded > shows placeholders for all visible specs		Output Screenshots Video

  cypress-in-cypress-component.cy.ts • 1 flaky test • app-e2e

View Output Video

Test		Artifacts
Cypress In Cypress CT > default config > redirects to the specs list with error if a spec is not found		Output Screenshots Video

The first 5 flaky specs are shown, see all 17 specs in Cypress Cloud.

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[warrensplayer]

I like the direction Mike was going with his comment about a more generic approach, but I wonder if this is a little bit of an AHA scenario. I am fine with your original specific solution, but can go along with the majority if we want to keep the current implementation.

[astone123]

Tested this out and it looks good to me. Just one minor comment

[astone123]

@warrensplayer agreed, I think this fills the use case that we need right now - if we find that later we need to do this again, at that point we should make it more generic. At this time I don't see a reason to do that

Out of Office for re-review and discussed in other reviewer comments.

[cypress-bot]

Released in 12.14.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v12.14.0, please open a new issue.