https://github.com/danman113/selenium-video-node-issue
https://github.com/danman113/selenium-video-node-issue
Last synced: 12 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/danman113/selenium-video-node-issue
- Owner: danman113
- Created: 2016-06-22T01:52:47.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-06-22T02:17:14.000Z (over 9 years ago)
- Last Synced: 2025-01-16T05:55:27.560Z (about 1 year ago)
- Language: Shell
- Size: 7.34 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# selenium-video-node-issue
##What it is
I basically just ripped the dockerfiles from [docker-selenium](https://github.com/SeleniumHQ/docker-selenium/) (specifically the nodeHub,nodeBase,nodeChrome and nodeFirefox) and added a few shell scripts to build and start the docker nodes.
I built this on osx, so there might be some small issues with the commands I used on linux
##How to start it
First install docker on your machine.
Then simply run:
`./buildContainers.sh`
This should download and install all of the dependencies (ubuntu, java, .etc) as well as install chrome.
Next run:
`./start.sh`
This will start the selenium-hub, and then start the firefox and chrome nodes and link them to the selenium-hub.
You can verify that these are working by running
```
#makes sure that docker is linked in your current enviroment
docker-machine start
docker-machine env
eval "$(docker-machine env default)"
#checks all docker processes
docker ps -a
```
##Getting the error
To actually get the chrome node to crash, send any google chrome test to the hub (to get the ip, run `docker-machine ip`).
I used `python test_docker_video.py`.
This will crash the node. To get the logs from the crashed node run:
`docker logs c1`
This will copy the stdout of the docker-container running the chrome node to your stdout.
#Finally, thanks a lot aimmac23. I owe you a coffee.