MarketSquare / MarketSquare/webdrivermanager
Webdrivermanager can not detect chrome version
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 104
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
We are using webdrivermanager command-line options when running tests on docker and recently started getting an issue, where webdrivermanager can not detect the correct chrome version. So it downloads the latest, and sometimes tests fail because of version mismatch
```
Step 11/29 : RUN webdrivermanager chrome --linkpath AUTO
09:35:34 ---> Running in 03faac027e3a
09:35:34 Error, unable to read current browser version
09:35:34 Failed to parse compatible version: Error, unable to read current browser version
09:35:34 Error, unable to read current browser version
09:35:34 Failed to parse compatible version: Error, unable to read current browser version
09:35:35 Downloading WebDriver for browser: "chrome"
09:35:35
0%| | 0/5945 [00:00
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The reported entry point is `webdrivermanager chrome --linkpath AUTO` in a Docker build; begin by reproducing it against Chrome 92.0.4515.107 and inspect the version-detection path. Done means the command detects the installed browser version and downloads a compatible driver instead of version 93.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100