#55657: test: wait for custom-protocol extension background readiness
Merged
Description of Change
Addresses intermittent Windows timeouts in the custom-protocol extension spec that remained after isolating fixture profiles.
loadExtension() can resolve before the MV3 background worker has registered its message listener. The fixture now waits for an explicit readiness announcement from the worker before navigating to the custom-protocol page. The readiness listener is attached before loading the extension so an early announcement cannot be missed.
The fixture runner also waits for process closure, checks exit status, and includes captured stdout/stderr in failure diagnostics.
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
-
npm testpasses - tests are changed or added
- PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, past tense, and no longer than 80 characters.
Release Notes
Notes: none
Backports
Semver Impact
Major
Breaking changes
Minor
New features
Patch
Bug fixes
None
Docs, tests, etc.
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron