Support for multiple browsers in one run
See original GitHub issueWhat would you like?
I would like to configure Cypress like this:
cypress run --browsers chrome,firefox
This would
- run the test suite in both browsers.
- It would not stop if one of those fail
- it would report test results and videos/screenshots for both of them, prefixed with the browser / in a sub directory with the name of the browser
Why is this needed?
We run Cypress in a cypress docker container to run the tests by Ops on other systems and mount the test results on the hosts file system. I’ve spent considerable amount of time to do this properly to run Cypress twice and have all test reports properly available on the host.
It would be a lot easier, if cypress would support that out of the box. And I could assume that this is actually a valid use case to run a suite with different browsers
Other
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top 10 Cross Browser Testing Tools In 2023 (Latest Ranking)
Given below is a list of all cross-browser compatibility testing tools available online for testing websites on multiple browsers.
Read more >Cross Browser Compatibility Testing beyond Chrome
Instant access to 3000+ real browsers and devices to run a cross browser compatibility test for your website. No setup is required.
Read more >Introduction to cross-browser testing - Learn web development
Cross-browser testing is the practice of ensuring that a website works across various browsers and devices. Web developers should consider:.
Read more >Cross Browser Testing - Cypress Documentation
Cypress has the capability to run tests across multiple browsers. Currently, Cypress has support for Chrome-family browsers (including Electron and.
Read more >Running the test on multiple browsers - ADM Help Centers
After you create a single test of your application or Web page to use in different browsers, you still must run it to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey @jwedel, our “Fire Watch” stage is an internal process we’re using to triage incoming issues from the community. We have a group of people representing each of the teams working on the open-source app, and they help to triage, reproduce, and route issues to the team best suited to address them. This issue was routed to my team and came up during a backlog grooming meeting today.
Since we have a pretty active community here on GitHub, sometimes we do miss tags in comments, so I apologize for the delay in getting back to you. The primary focus for a while now (especially this last month) has been in releasing 10.0 and fixing any high-priority issues reported against it. For this specific issue you’ve logged, it seems appropriate for a product manager to review the proposal. I’ve flagged it for product review to get it on their radar. You can expect some discussion (likely from @pstakoun soon). For full transparency considering our current roadmap, I thought I’d also call out that this will be a low-priority enhancement request at this time. Product review discussions, or even more interest from the community, however, are things that may impact prioritization, so consider priority to be a pretty fluid thing.
You can configure where results are written, or have a simple script move them between runs