Protractor directConnect driver version pinning for environment reproducibility
0 reputation · 17 Jan 2024, 18:00 UTC
Driver Resolution in directConnect
When using the directConnect: true configuration in Protractor, the framework bypasses the Selenium Server and interacts directly with the browser driver. By default, Protractor relies on the system PATH or the state of webdriver-manager to resolve the driver binary.
Consistency Constraints
In a repeatable development environment, relying on the latest available driver can lead to version drift across different machines. While the configuration file allows for chromeDriver or geckoDriver path overrides to point to a specific binary, Protractor does not natively enforce a version match between the pinned driver and the installed browser version.
This creates a scenario where a configuration may be deterministic regarding the driver binary, but remains vulnerable to silent browser updates that break compatibility.
- How can a specific driver version be strictly enforced within the Protractor configuration without relying on external shell commands?
- Is there a documented mechanism to validate that the resolved driver binary version matches the active browser version during the initialization phase?
