You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In our tests we need to run a page using different users, and we used to reset context, and set new HTTP credentials. But recent version of Playwright warns that
warning: method |context.setHTTPCredentials()| is deprecated. Instead of changing credentials, create another browser context with new credentials.
Describe the solution you'd like jestPlaywright.resetContext() creates new context already, but with context options defined in its initial config. It would be nice if this method can accept additional context options, and merge them with initial options.
Describe alternatives you've considered
We are already using custom Playwright environment, and we can just overwrite resetContext method with our custom implementation, but we believe this feature would give value to entire community.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In our tests we need to run a page using different users, and we used to reset context, and set new HTTP credentials. But recent version of Playwright warns that
warning: method |context.setHTTPCredentials()| is deprecated. Instead of changing credentials, create another browser context with new credentials.
Describe the solution you'd like
jestPlaywright.resetContext()
creates new context already, but with context options defined in its initial config. It would be nice if this method can accept additional context options, and merge them with initial options.Describe alternatives you've considered
We are already using custom Playwright environment, and we can just overwrite
resetContext
method with our custom implementation, but we believe this feature would give value to entire community.The text was updated successfully, but these errors were encountered: