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
test(functional): Add real test for 'web-ext run -t chromium'
The existing unit tests for web-ext run -t chromium are at
tests/unit/test-extension-runners/test.chromium.js but are testing
implementation details without verifying that Chrome is actually going
to launch the extension.
Before refactoring the implementation as needed to support Chrome 137+
and later, this introduces a unit test that verifies the behavior
against the real Chrome (skipped by default), and a fake Chrome binary
that behaves like the real Chrome binary where relevant.
This will help us with catching regressions in the implementation and/or
downstream dependencies (chrome-launcher).
These Chrome behavior has been verified across Chrome 69, 70, 75, 77,
88, 100, 122, 125, 126, 134, 139.
The auto-reload case of the "real Chrome" test in Chrome 134 requires
manual intervention in the form of visiting chrome://extensions/,
enabling 'Developer Mode' and then manually reloading the extension, for
the following reasons:
- The bundled "web-ext Reload Manager Extension" uses Manifest Version
2, which is disabled by default in recent Chrome.
- When 'Developer Mode' is off (by default), an attempt to reload
extensions that were loaded with --load-extension causes the extension
to be disabled.
These two issues will be resolved once we switch to the new CDP-based
method of loading Chrome extensions.
0 commit comments