Skip to content
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

Support for multiple browsers in one run #21387

Open
jwedel opened this issue May 9, 2022 · 6 comments
Open

Support for multiple browsers in one run #21387

jwedel opened this issue May 9, 2022 · 6 comments
Labels
E2E Issue related to end-to-end testing type: feature New feature that does not currently exist

Comments

@jwedel
Copy link

jwedel commented May 9, 2022

What 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

@cypress-bot cypress-bot bot added the stage: investigating Someone from Cypress is looking into this label May 9, 2022
@mjhenkes mjhenkes added type: enhancement Requested enhancement of existing feature E2E-core labels May 10, 2022
@cypress-bot cypress-bot bot added stage: routed to e2e-core and removed stage: investigating Someone from Cypress is looking into this stage: routed to e2e-core labels May 10, 2022
@jwedel
Copy link
Author

jwedel commented May 17, 2022

@mjhenkes Hi, just for my understanding, what does the label "fire watch" mean? Thx

@rockhold
Copy link

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.

@pstakoun
Copy link
Contributor

pstakoun commented Jun 23, 2022

@jwedel I'm curious to learn why you need both browsers in a single run, rather than using our provided grouping mechanism via --group to combine runs on multiple browsers into a single run. Alternatively, would it be suitable to simply run something like cypress run --browser chrome && cypress run --browser firefox?

@jwedel
Copy link
Author

jwedel commented Jun 30, 2022

@pstakoun Thanks for you suggestions. I am really open to find a solution that is already there :)

Also after reading the grouping mechanism, I am not sure how this can be leveraged to call Cypress once and have it output reports and videos for two browsers.

Alternatively, would it be suitable to simply run something like cypress run --browser chrome && cypress run --browser firefox?

Cypress is executed from an image and gets things like which browser to run from the command line. So it's not that easy to do this in a configurable way. Also, wont it overwrite the the result videos e.g.?

@csvan
Copy link

csvan commented Jul 2, 2022

You can configure where results are written, or have a simple script move them between runs

@mschile mschile added triage and removed triage labels Aug 18, 2022
@nagash77 nagash77 added E2E Issue related to end-to-end testing and removed E2E-core labels Nov 8, 2022
@manoj-fd
Copy link

Hi @jwedel , I am currently exploring the option to run multiple browser in cypress, just noticed your ticket here, are you able to find any existing solution to support multiple browser, i see few suggestions grouping mechanism and combining cypress runs, would like to understand you got any other solution

@jennifer-shehane jennifer-shehane added type: feature New feature that does not currently exist and removed priority: low type: enhancement Requested enhancement of existing feature labels Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E2E Issue related to end-to-end testing type: feature New feature that does not currently exist
Projects
None yet
Development

No branches or pull requests

10 participants