Browser Mode: Allow extended configuration of provider

[JoaoCnh]

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 a locator.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:

• actionTimeout - optional and number
• expectTimeout - optional and number

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

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[hi-ogawa]

It's possible to define a specific timeout for an expect

I don't think expectTimeout would apply to Vitest? I would assume that's their async assertion's timeout, so for us, that would be probably expect.element(), which can be already configured by expect.poll.timeout.

[hi-ogawa]

I think actionTimeout is only anomaly for playwright since it's probably more like test runner concern than pure browser driver, so they didn't include it in their BrowserContextOptions.

@JoaoCnh Do you see anything missing for Vitest's provider options other than actionTimeout?

[JoaoCnh]

Hey, at the moment the only thing other than actionTimeout that I encountered was the ability to activate playwright tracing for debugging purposes in CI. But not sure what are the plans for Vitest regarding that in the future.

[hi-ogawa]

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.