You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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:
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?
The text was updated successfully, but these errors were encountered: