-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Browser Mode: Allow extended configuration of provider #6983
Comments
I don't think |
I think @JoaoCnh Do you see anything missing for Vitest's provider options other than |
Hey, at the moment the only thing other than |
Indeed, it looks like https://playwright.dev/docs/api/class-testoptions#test-options-trace is another diff between https://playwright.dev/docs/api/class-testoptions and https://playwright.dev/docs/api/class-browser#browser-new-context I like playwright's trace too but I'm not sure yet how we can integrate that. I would assume at least we would rely on their UI to preview trace, but maybe it's possible to generate that during Vitest browser mode. |
Clear and concise description of the problem
Running test suites in CI is quite different from running them on a local machine. CI is quite often slower and locators take more than the default 1000ms to locate elements or to perform actions (click, hover, etc).
It's possible to define a specific timeout for an
expect
or alocator.click
for example but it would be nice to be able to set larger timeouts at a config level for when the tests run in CI.Suggested solution
add new properties in the
browser
config for the following:This would under the hood configure the correct provider configurations if possible.
Here's doc ref to Playwright test configuration
Alternative
Allow full customisation of test configuration.
Right now we're allowed to extend launch options and browser context options on playwright for example but we could extend this configuration to Test Options
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: