Skip to content

Commit d2a8ba8

Browse files
ckshobhatimdavish
authored andcommitted
Test doc update (#181)
* Update test doc with the problems faced running e2e test * update the text
1 parent e7c5892 commit d2a8ba8

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed

docs/TESTS.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,3 +3,36 @@
33
## End-to-End (e2e) tests
44

55
You can run the e2e tests with `yarn e2e`. This will stop all docker containers, clear the necessary ports, start the containers and the app, and then run the tests.
6+
7+
# Problems
8+
9+
## e2e cases failed with "Connection refused! Is selenium server started"
10+
11+
**Problem**:
12+
13+
```
14+
{ Error [ERR_UNHANDLED_ERROR]: Unhandled error. ([object Object])
15+
at ClientManager.emit (events.js:140:19)
16+
at Nightwatch.<anonymous> .....
17+
.....
18+
context:
19+
{ message: 'Connection refused! Is selenium server started?\n',
20+
data: { value: [Object], status: 33 } } }
21+
.....
22+
```
23+
24+
**Solution**:
25+
```
26+
- Ensure the required version of selenium package is installed
27+
yarn list | grep selen
28+
29+
- Ensure to check selenium server is not running prior to starting the e2e tests.
30+
ps -ef | grep sele
31+
32+
- Ensure the server is started when "yarn e2e" is run by running
33+
ps -ef | grep sele
34+
502 44074 44068 0 12:23PM ttys008 0:00.06 /usr/bin/java -jar ./node_modules/selenium-server/lib/runner/selenium-server-standalone-3.8.1.jar -port 4444
35+
36+
Ensure the pid on the output matches the one displayed when yarn e2e was started.
37+
Look for line that says "Starting selenium server... started - PID: 44074"
38+
```

0 commit comments

Comments
 (0)