Skip to content

Commit e18214e

Browse files
committed
add tests/troubleshooting.md guide on how to get E2E tests to run
1 parent 0b8910a commit e18214e

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

tests/troubleshooting.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# Troubleshooting
2+
3+
## Webdriver
4+
5+
If you're seeing errors like
6+
7+
```sh
8+
ERROR dash.testing.browser:browser.py:433 <<<Webdriver not initialized correctly>>>
9+
```
10+
11+
or
12+
13+
```sh
14+
E selenium.common.exceptions.WebDriverException: Message: unknown error: cannot find Chrome binary
15+
```
16+
17+
try manually installing `chromedriver` and/or `google-chrome`. On macOS, this can be done with `brew`:
18+
19+
```sh
20+
brew install --cask chromedriver
21+
brew install --cask google-chrome
22+
```
23+
24+
macOs may complain that it cannot verify the security of these executables in which case you can manually override and give permission in 'System Preferences > Security & Privacy'.

0 commit comments

Comments
 (0)