chore: adding command log to protocol

[mschile]

Additional details

• Calls protocol.commandLogAdded when the Cypress.on(log:added) event is triggered.
• Calls protocol.commandLogChanged when the Cypress.on(log:changed) event is triggered.
• Updated tests that were spying/stubbing Cypress.backend to not log since that will now cause an infinite loop where we log the spy/stub and then call the backend again for the protocol which causes a log for the spy/stub and so on.

Steps to test

• Clone the cypress-services repo and checkout mschile/protocol/add_command_log
  • Run yarn
  • Run yarn watch-protocol
• Set CYPRESS_LOCAL_PROTOCOL_PATH to the path to cypress-services/packages/app-capture-protocol/dist/index.js
• Clone the cypress repo and checkout mschile/protocol/add_command_log
  • Run yarn
  • Execute cypress run on a project in record mode with DEBUG set to cypress:*protocol* and ensure the command:log events are added to the database.

How has the user experience changed?

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]

3 flaky tests on run #45282 ↗︎

0

5121

74

0

3

Details:

more backend fixes
Project: cypress	Commit: 202f8921cc
Status: Passed	Duration: 14:49 💡
Started: Apr 5, 2023 3:37 AM	Ended: Apr 5, 2023 3:52 AM

  cypress/e2e/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

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

[cypress-bot]

Released in 13.0.0.

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