blueimp / nightwatch Goto Github PK

Great Dockerfile, and thanks for putting this together! The example works like a charm and it was easy to port to my project. But I was wondering if you could increase the timeout in wait-for.sh from 10 seconds to 60 seconds? My app container is a React application that must be bundled into a production build before getting served by my Express server (unlike in the example that uses an nginx image that serves /app/index.html), and this process can take between 20-40 seconds.

And also, the nightwatch container installs via apk nodejs-lts, but I am using some ES6 features in my tests that are not supported by Node LTS. Maybe this is not possible though as I could not find a later version of Node in the apk directory.

Thanks again!

I got this error while trying to run --rm nightwatch

There was an error while starting the test runner:

Error: Cannot read source folder: /home/node/examples/tests
    at /usr/lib/node_modules/nightwatch/lib/runner/run.js:200:21
    at /usr/lib/node_modules/nightwatch/lib/runner/walk.js:97:18
    at FSReqWrap.oncomplete (fs.js:82:15)

I could not find dir examples/tests, did i miss any step ?

ps: i am using docker-engine 1.7 and compose 1.3

hi i used the command "docker-compose run --rm nightwatch"
ERROR: Cannot start service nightwatch: oci runtime error: container_linux.go:265: starting container process caused "exec: "entrypoint": executable file not found in $PATH"

This is the actual issue behind blueimp/chromedriver#3

When the chromedriver image is updated on dockerhub it is automatically released to all users of this repo, even if the change is not backwards-compatible with the current pinned version of the nightwatch container.

I get a timeout when trying to docker-compose run --rm nightwatch:

Starting nightwatch_chromedriver_1 ... 
Starting nightwatch_nginx_1 ... done
Waiting for nginx:80 to become available ... done
Waiting for chromedriver:4444 to become available ... done
Waiting for chromedriver:6060 to become available ... timeout

How can fix this? Where does this port even come from? The blueimp/chromedriver package only specifies 4444 ...

Thank you!

Hi,

I like so much your project but I was wondering if ther is any configuration to change chromedriver resolution. I would like to check the responsive design of my web.

Thanks so much.

Hi,
I think that it would be useful if we could pass command line options to the nigthwatch instance. http://nightwatchjs.org/guide#command-line-options.

Thanks in advance.

Hello,

I'm trying to configure the nightwatch file and docker-compose file to run against a server on the host.

For example, I'm serving up the site at localhost:4444 on my machine and I would like nightwatch to use that instead of the http://nginx URL.

I have tried exposing ports configuring networks but to no avail. How would I go about this?

Hi,

I am running into issues running tests in parallel. If I updated the "test_workers" param to true in the nightwatch.json and run
docker-compose run --rm nightwatch

Both sample tests I have configured to run fail immediately, without starting the tests. I have looked at the docker containers and as much logs as possible but I have found no relevant information.

I have gotten tests running in parallel outside of docker, so wondering if you have any advice on how to run tests across a number of workers within the docker container?

Thanks,
Eric

I am getting exception while running the docker compose command for running the test from my existing night watch project

There was an error while starting the test runner:

Error: Cannot read source folder: /home/node/examples/tests
at /usr/lib/node_modules/nightwatch/lib/runner/run.js:200:21
at /usr/lib/node_modules/nightwatch/lib/runner/walk.js:97:18
at FSReqWrap.oncomplete (fs.js:82:15)

Please look into this issue

Hi,
can you please update the Docker Hub image with the latest version please?

Hi @blueimp! Thank you for a great tool! I have a question regarding using this project in continuous integration, in my case Circle CI. Have you used it in the CI environment? I'm struggling a bit in either I should keep using docker compose or just rely on CI's default docker image? Please advice if you have the context on it.
Thank you!

Is there any particular reason for mounting video recorder module as a volume instead of installing it right into the image?

Currently the tests run on chrome driver so is it possible to make different device configuration like android,firefox,ios to test further more?

Hi @blueimp,
thanks this awesome image.
I tried it but I got error.
Command:

git clone https://github.com/blueimp/nightwatch.git
cd nightwatch
docker-compose run --rm nightwatch

Result:

Waiting for app:80 to become available ... done
Waiting for chromedriver:4444 to become available ... done
Waiting for chromedriver:6060 to become available ... done

[Failure] Test Suite
========================

There was an error while starting the test runner:

Error: EACCES: permission denied, mkdir '/home/node/videos'
    at Error (native)
    at Object.fs.mkdirSync (fs.js:794:18)
    at mkdirp (/home/node/node_modules/nightwatch-video-recorder/index.js:20:8)
    at Object.module.exports.start (/home/node/node_modules/nightwatch-video-recorder/index.js:41:7)
    at Object.module.exports.beforeEach (/home/node/globals.js:5:42)
    at TestSuite.<anonymous> (/usr/lib/node_modules/nightwatch/lib/runner/testsuite.js:459:16)
    at TestSuite.makePromise (/usr/lib/node_modules/nightwatch/lib/runner/testsuite.js:511:8)
    at TestSuite.adaptGlobalHook (/usr/lib/node_modules/nightwatch/lib/runner/testsuite.js:435:15)
    at TestSuite.globalBeforeEach (/usr/lib/node_modules/nightwatch/lib/runner/testsuite.js:427:15)
    at TestSuite.run (/usr/lib/node_modules/nightwatch/lib/runner/testsuite.js:203:10)

Do you have any idea, what is the problem? I see that it has no access for videos folder but I don't know why.

Thanks!

You aren't very good at obfuscating your code are you ? All I want is my money back and I will go away, simple.