Protractor directConnect driver version pinning for environment reproducibility

Enforcing Driver Versions in directConnect

Protractor does not provide a native configuration property to strictly enforce a specific driver version number at runtime. When directConnect: true is enabled, Protractor resolves the driver binary via the system PATH or the specific path provided in the chromeDriver or geckoDriver configuration properties. It does not verify the version of the binary it finds against a required version string.

Implementation for Version Pinning

To ensure environment reproducibility without relying on external shell scripts, you must explicitly define the path to a known-version binary in your protractor.conf.js. This bypasses the default search logic and ensures the same binary is used across all environments that share the same directory structure.

exports.config = {
  directConnect: true,
  capabilities: {
    browserName: 'chrome'
  },
  // Explicitly pin the binary path
  chromeDriver: '/usr/local/bin/chromedriver-114.0.5735.90',
  onPrepare: async function() {
    // Custom validation logic goes here
  }
};

Validating Browser-Driver Compatibility

There is no documented internal mechanism in Protractor to automatically validate that the resolved driver matches the active browser version during initialization. If a browser auto-updates, Protractor will typically throw a SessionNotCreatedError only after attempting to launch the session.

To implement a pre-flight check, you can use the onPrepare lifecycle method to query the driver's capabilities or execute a version check. Since the driver is already initialized by the time onPrepare runs, you can verify the session capabilities:

• Capability Check: Use browser.capabilities() to inspect the browserVersion returned by the driver.
• Manual Comparison: Compare this value against a hardcoded expected version string and throw a descriptive error to stop the suite immediately if they mismatch.

Assumptions and Limitations

This approach assumes that the driver binary is pre-provisioned at the specified path (e.g., via a Docker image or a CI pipeline step). Because Protractor is largely deprecated, it lacks the dynamic driver management found in newer tools like WebDriver Manager for Java or the built-in managers in Playwright/Cypress.

Diagnostic Detail Required: Are you utilizing a containerized environment (Docker) or a shared VM for these executions? If you are using Docker, pinning the driver is best handled via the image layer rather than the Protractor configuration.