-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement backend events for stubbing/spying WebSockets #7655
Comments
This would be a game-changer for test automation. I can't wait for this to land! Let me know if you'd like me to test a preview PR! |
any update on this one guys, when can we expect this ? |
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. |
this feature would be awesome, bump for a stale bot |
Would be awesome to support this! |
Would be so great to have this! We are waiting on data from a websocket to refresh and right now we have to go through hurdles to update hidden dom elements on the page so that we can notify cypress that the data is done loading.... it's beyond kludgy. Having a "cy.intercept" that works with websocket messages would be so helpful. |
Build out backend events to support stubbing/spying WebSockets for #199
add:route
for matching on WebSocketsws:connect
CyIncomingRequest, CyWebSocket
ws:connect:continue
CyIncomingRequest
ws:disconnect
CyWebSocket
ws:frame:outgoing
CyWebSocket, CyWebSocketMessage
ws:frame:outgoing:continue
CyWebSocketMessage
ws:frame:incoming
CyWebSocket, CyWebSocketMessage
ws:frame:incoming:continue
CyWebSocketMessage
Depends on #687
The text was updated successfully, but these errors were encountered: