Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added service container for Selenium standalone with Chrome #519

Merged
merged 2 commits into from
Jan 1, 2017

Conversation

edmundluong
Copy link
Contributor

@edmundluong edmundluong commented Dec 31, 2016

Resolves #356

Added Selenium using the official Selenium docker images from https://github.com/SeleniumHQ/docker-selenium

The Selenium server is served on port 4444

@appleboy
Copy link
Member

Can you update the README file?

@edmundluong
Copy link
Contributor Author

@appleboy Updated, thanks

@philtrep philtrep merged commit 2fc3919 into laradock:master Jan 1, 2017
@philtrep
Copy link
Member

philtrep commented Jan 1, 2017

@edmundluong thanks for your contribution!

@symbios-zi
Copy link

@edmundluong Hello. Do you use it for codeception?
I am trying to configure it for use acceptance tests. It requires selenium web driver or phantomJS.

But the problem is website url which unavailable inside selenium container.

@chkm8
Copy link
Contributor

chkm8 commented Jun 7, 2017

Hi, im trying to integrate browser testing with dusk and selenium, when I run php artisan dusk , all my test are passing but I cant see the browser being loaded or open. Also there is no screenshots saved in test/Browser/screenshots folder if test failed.

Steps: (scripts below are excuted inside workspace - docker-compose exec workspace bash)
1-docker-compose up -d apache2 selenium
2-added/setup dusk (php artisan dusk:install)
3-created browser test
4-php artisan dusk
->My sample regression does succeed but I can't see the browser being tested.
--visited the selenium url: http://localhost:4444/wd/hub
--I can only see a session menu

What am I missing here? Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants