Replies: 2 comments 1 reply
-
We've been making several changes to the way tabs work within Cypress with the aim of having a beta It was never intended for Cypress to interact in any way with other tabs and we even display a warning when opening new tabs within Cypress discouraging the use of other tabs. With the work around getting the plugin to function and wanting the tabs to not interact any way with Cypress test runs, we've closed some situations where there were interactions between the new that was never intended and actually causing issues in our proxy logic like #28188. The 13.6.0 release today will see some additional changes to how tabs work in order to further faciliate the plugin to offer some forms of multi-tab testing, like closing all tabs in between each test run. 13.6.0 contains the final changes we intended to make for the beta release of the plugin, wherein we will gather feedback from the community. We'd love to hear your feedback on how these changes affect your use of Cypress so that we can use that feedback to deliver a better product. |
Beta Was this translation helpful? Give feedback.
-
The @cypress/puppeteer plugin has been released btw, which is what these changes were in preparation for. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I wanted to raise a discussion to get some insights on how Cypress plans to support network traffic on other tabs.
In previous versions of Cypress, traffic on any tab/page of the browser were handled the same. If you had an intercept for a test it would also be applied to other tabs in the browser.
I understand that the cypress browser loads the suite page as it's main entry point for running tests. However there are other apps which also benefited from running through Tabs such as lighthouse. It was pretty useful having a single mocking solution to run e2e, visual and performance tests. If Cypress has no plans to support other tabs or keep them serperate to the cypress testing suite it would be good to know that sooner rather than later.
Over that past few versions of Cypress the network behaviour around tabs has changed quite dramatically.
Going from Slow to Slower, missing headers and now behaving as if just a regular Chrome tab.
What is the expected behaviour for a new tab in the Cypress browser?
Looking at recent Pull requrest comments it looks like the aim is to have new tabs behave as normal Tabs.
Beta Was this translation helpful? Give feedback.
All reactions