You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using this chromedriver path in the tests, you can use the following code to get the path of the chromedriver:
Getting the path of chromedriver
To be able to get the path of where chromedriver exist in non-node libraries each library can read the .env file created by browser-driver-manager and get the path from there.
Epic https://github.com/dequelabs/axe-api-team/issues/497
Proposal: https://github.com/dequelabs/axe-api-team/blob/ac01e14fc119965e2ccb4bd834a5554cedb275dd/proposals/technical-requirements/chrome-driver-download-steps-in-central-place.md
Upgrade version of
browser-driver-manager
in each repository CI configurationbrowser-driver-manager
should upgrade its version so that the repos can use the new chrome driver installation method.Update repos that downloads
chromedriver
Each repo that downloads
chromedriver
will need to do it usingbrowser-driver-manager
Please reference Usage guide
Usage
When using this chromedriver path in the tests, you can use the following code to get the path of the chromedriver:
Getting the path of chromedriver
To be able to get the path of where chromedriver exist in non-node libraries each library can read the
.env
file created bybrowser-driver-manager
and get the path from there.NPM based packages
Non-NPM based packages (Psuedo code)
The text was updated successfully, but these errors were encountered: