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

Question: How does this work? #28

Open
Gobliins opened this issue Sep 4, 2017 · 2 comments
Open

Question: How does this work? #28

Gobliins opened this issue Sep 4, 2017 · 2 comments

Comments

@Gobliins
Copy link

Gobliins commented Sep 4, 2017

So i have a meteor/node app and want to do some automated ui tests with a headless chrome.

Normally i would install prortactor per npm and write some tests. For my UI tests i would use a docker which runs a standalone chrome since i have no gui. In my protractor config i configure protractor to use my selenium chrome. Then i run protractor.

So i am a bit confused about this project.

How is the workflow of this meant to be?

I have my node/meteor server running.
I have this docker image running... and then what?

@jciolek
Copy link
Owner

jciolek commented Oct 4, 2017

You should be able to use this image as a drop-in replacement for Protractor but with built-in Chrome, so to speak. So, in your example, you run node/meteor and then run this image passing it your protractor config. Let's say your config is called protractor-conf.js, the you would run it like so:

docker run -it --privileged --rm --net=host --shm-size 2g -v $(pwd):/protractor webnicer/protractor-headless protractor-conf.js

I hope that helps.

@jciolek
Copy link
Owner

jciolek commented Oct 4, 2017

I'm leaving this open as a reminder to add an example to README.

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

No branches or pull requests

2 participants