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.
I want to test a script in a service worker's both presence and absence. However, there are something blocking this:
When using the sw option, playwright-test registers the service worker immediately on the page load.
Unlike workers, service workers can't be terminated.
Using a controllable iframe or new window doesn't help, it inherits the service worker.
When not using the sw option, I have to create my own bundle to pass it as an asset to playwright-test.
So there seems no easy way to tun tests in both the service worker's presence and absence.
Describe the solution you'd like
An option, that stops playwright-test from registering the service worker but keeps playwright-test preparing the bundle. Also, the path of the bundled sw should be exposed somewhere (maybe like PW_TEST.env.swURL) so that we can register it later. The user will have more control on the register option, too.
Describe alternatives you've considered
Stop using sw option, and prepare my own bundle for service worker before running playwright-test.
Additional context
None yet.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I want to test a script in a service worker's both presence and absence. However, there are something blocking this:
sw
option,playwright-test
registers the service worker immediately on the page load.sw
option, I have to create my own bundle to pass it as an asset toplaywright-test
.So there seems no easy way to tun tests in both the service worker's presence and absence.
Describe the solution you'd like
An option, that stops
playwright-test
from registering the service worker but keepsplaywright-test
preparing the bundle. Also, the path of the bundled sw should be exposed somewhere (maybe likePW_TEST.env.swURL
) so that we can register it later. The user will have more control on the register option, too.Describe alternatives you've considered
Stop using
sw
option, and prepare my own bundle for service worker before runningplaywright-test
.Additional context
None yet.
The text was updated successfully, but these errors were encountered: