#55524: docs: explain ChromeDriver arguments during testing
Description of Change
Fixes #31769.
Document that ChromeDriver adds arguments to Electron's process.argv, including
switches and a positional startup URL. Explain why these can break strict argument
parsing, and recommend handling only known driver-added arguments in test startup
while retaining validation of application arguments.
Validation on Linux x64 with Electron 45.1.0, electron-chromedriver 45.1.0
(ChromeDriver 156.0.8078.49), selenium-webdriver 4.52.0 and yargs 18.2.0:
- Reproduced strict-parser startup failure under ChromeDriver.
- An explicit test-only schema/filter restored a working WebDriver session;
application-option typos and an unlisted switch still failed validation. npm run lint:docspassed on the base and this change, with the same existing
crash-reporter.mdAPI-history warning.
No native Electron build, full runtime suite, Windows/macOS run or WebdriverIO
service test was performed for this documentation-only change.
AI assistance: OpenAI Codex assisted with investigation, drafting and validation;
Gemini via Antigravity and Claude Opus via ATD provided independent review.
Checklist
- I have filled out the PR description
- I have reviewed and verified the changes
- Relevant documentation follows the documentation style guide
Release Notes
Notes: none
Backports
Semver Impact
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