Create diagnostic which suggests uninstalling chromedriver
What does this merge request do and why?
Create diagnostic which suggests uninstalling chromedriver
Chromedriver is not needed any longer and having it installed might lead to problems if Selenium prefers it over the version shipped with SeleniumManager.
See also: !3280 (merged)
How to set up and validate locally
- Check out branch
brew install chromedriver-
gdk doctor=> Reports that chromedriver can be uninstalled brew uninstall chromedriver-
gdk doctor=> Is happy
Impacted categories
The following categories relate to this merge request:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.
Merge request checklist
-
This change is backward compatible. If not, please include steps to communicate to our users. -
Tests added for new functionality. If not, please raise an issue to follow-up. -
Documentation added/updated, if needed. -
Announcement added, if change is notable. -
gdk doctortest added, if needed. -
Add the ~highlightlabel if this MR should be included in theCHANGELOG.md.
Edited by Lukas 'ai-pi' Eipert