Skip to content

cli: allow --chromedriver-path to work in chrome (not just chrome-headless) #1189

@straker

Description

@straker

When trying to run the cli with--browser=chrome and having an out-of-date chromedriver, you get the following error:

Error: session not created: This version of ChromeDriver only supports Chrome version 128
Current browser version is 138.0.7204.158 with binary path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

Please use browser-driver-manager to install matching versions of Chrome and ChromeDriver:

        $ npx browser-driver-manager install chrome

        This will install the latest synced versions. You may install specific synced versions using

        $ npx browser-driver-manager install chrome@<version>

        where <version> is a specific version, e.g. 123.45.67, or a channel, e.g. canary.

        You may also pass the `--chromedriver-path` option to axe:

        $ axe --chromedriver-path <path/to/chromedriver-executable>

However, if you follow the remediation steps and install chromedriver, the cli does not let you pass --chromedriver-path when using --browser=chrome. The codepath only uses the chromedriver path if you are in chrome-headless. This means there's no way to fix the issue as passing in the chromedriver-path does nothing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions