Akash Rathod a98c81bbbe
[ACS-8045] update chrome driver settings (#3862)
* [ACS-8045]update ACA chrome driver

* [ACS-8045]update ACA chrome driver to stable

* [ACS-8045]update ACA chrome driver script

* [ACS-8045]revert chrome driver script

* update webdriver tesst

* Update action.yml

* update webdriver command

* update webdriver new script

* remove chrome install step

* remove chrome webdriver update twice

* add chrome webdriver update step

* e2e run command update

* e2e run command update

* e2e run command update

* remove temp e2e
2024-05-31 10:11:43 +02:00

37 lines
1.8 KiB
Markdown

# Run protractor with newest webdriver locally
## Instruction
To download newest driver simply run script from its directory
`update-to-newest-webdriver.sh`
Command accepts one parameter to define what OS you are using. By default its set to `mac-x64`
Possible inputs `linux64, mac-arm64, mac-x64, win32, win64`
Example `./update-to-newest-webdriver.sh win64` - will set driver for windows
## How it works
1. The script removes your existing driver files from webdriver node_modules
2. Generates two new files (chrome_xml.js and update.js) that have updated methods needed to get the new driver
3. Replaces browser type depending on parameter
4. Copies and replaces the files to the webdriver node_modules
5. Executes command to to update-webdriver using updated code
## Troubleshooting
If the script fails for any reason. You can do some of these actions manually:
1. Find the two files (chrome_xml.js and update.js) in node_modules/webdriver-manager
2. Replace its contents with (chrome_xml_schema.js and update_schema.js) keep the original names.
3. Change version for specific OS in both files
chrome_xml.js -> ['platform'] == 'mac-x64' e.g. ['platform'] == 'win64' Line 70
update.js -> 'chromedriver-mac-x64' e.g 'chromedriver-win64' Line 240
4. Run standard command to update webdriver `./node_modules/webdriver-manager/bin/webdriver-manager update --gecko=false`
## Reason
Latest ChromeDriver Binaries https://googlechromelabs.github.io/chrome-for-testing/
Starting with M115 the latest Chrome + ChromeDriver releases per release channel (Stable, Beta, Dev, Canary) are available at the Chrome for Testing availability dashboard. For automated version downloading one can use the convenient JSON endpoints.
The older releases can be found at the Downloads page.
Note: Protractor is a depricated tool and this probably won't be fixed.