Closed leegee closed 7 years ago
How does your config file look like? How does the test file look like? Have you tried to log what happens in webdriver.js:769:24? I was starting with NW for the first time today and was able to get up and running within 5 minutes by following the docs.
Which docs dod you follow, please?
On Oct 7, 2017 06:13, "kontrollanten" notifications@github.com wrote:
How does your config file look like? How does the test file look like? Have you tried to log what happens in webdriver.js:769:24? I was starting with NW for the first time today and was able to get up and running within 5 minutes by following the docs.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nightwatchjs/nightwatch/issues/1608#issuecomment-334909056, or mute the thread https://github.com/notifications/unsubscribe-auth/AAfTMAcJzSKL4SUJXPzek71Qv5nv5TIzks5spvp4gaJpZM4PuvTF .
I can't really expect a test framework to handle Windows-specific WebDriver issues, so closing this. (It was a conflict between Selenium and Chromedriver versions, which I've seen a lot of with other WD projects, as well as in these GitHub issue archives -- if only there was a linked matrix of working versions. Ended up using webdriver-manager)
New user, familiar with Selenium, Protractor, etc, following the docs and Wiki.
OS: Windows 10, fully patched npm -v : 5.3.0 node --version : v8.5.0 Selenium version: various, including selenium-server-standalone-2.53.1.jar
Just noticed that after a pause, Selenium.jar outputs:
So, I I put a copy of a Chromedriver executable where nightwatch expects it (hope that can be customised?), and now a browser window opens, and I notice that the next error follows the same reporting pattern:
It would help if the docs could be a little more explicit.....