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

[Feature request] Running tests suites on multiples chromium browser with different executablePath #539

Closed
PaulRosset opened this issue Jan 18, 2021 · 2 comments · Fixed by #545
Labels
enhancement New feature or request

Comments

@PaulRosset
Copy link
Contributor

Is your feature request related to a problem? Please describe.

I would like to run tests in multiple similar environments.

For example, I would like to my test suite on Google Chrome thanks to the executablePath but also on Chromium Edge with a new executablePath

But I can't do that since it accepts only one instance of chromium based browser.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Running the same test suites on multiple same types of browsers with a different executablePath.

@PaulRosset PaulRosset changed the title Running tests suites on multiples chromium browser with different executablePath Running tests suites on multiples chromium browser with different executablePath Jan 18, 2021
@PaulRosset PaulRosset changed the title Running tests suites on multiples chromium browser with different executablePath [Feature request] Running tests suites on multiples chromium browser with different executablePath Jan 18, 2021
@mmarkelov mmarkelov added the enhancement New feature or request label Jan 18, 2021
@mmarkelov
Copy link
Member

@PaulRosset got your point and i just need to think about this feature. Maybe browsers should an array of object instead of string.

// jest-playwright.config
{
  ...
  browsers: [
    {
      browserType: 'chromium',
      // options here, like here
      launchOptions: {
        ...
        executablePath
     },
     'chromium'
  ]
}

@PaulRosset
Copy link
Contributor Author

yes, I was also thinking about that in terms of API.

It would allow us to consider firefox, webkit, and chromium only as "base" browser and allow us to fully use the power of executablePath.

Looks promising!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants