Skip to content

Conversation

Sujatha-Pushparaj
Copy link

I tried exactly what was given in the current version of documentation for test automation using selenium on the nw.js application. According to the documentation, copying only the chrome driver from the SDK build to the application directory should work. But it didn't work for me and was throwing an error saying chrome not reachable. Fortunately, it worked when I built the application with the SDK version of nw.js. So I made a correction in the documentation on the same.

I tried exactly what was given in the current version of documentation for test automation using selenium on the nw.js application. According to the documentation, copying only the chrome driver from the SDK build to the application directory should work. But it didn't work for me and was throwing an error saying chrome not reachable. Fortunately, it worked when I built the application with the SDK version of nw.js. So I made a correction in the documentation on the same.
### Installing

* Download ChromeDriver from NW.js website. It's in the SDK build.
* Extract the package and place `chromedriver` under the same dir that contains the NW.js binaries: `nw` for Linux, `nw.exe` for Windows, or `node-webkit.app` for Mac.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this removed?

Copy link
Author

@Sujatha-Pushparaj Sujatha-Pushparaj Jan 6, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The instructions provided currently is not working when I tried to automate tests using selenium in nw version of my application. While debugging I found it working when the application is built with SDK version of nw. So simply copying the 'chromedriver' from SDK version to application built with production version of nw doesn't seem to work.

@stale
Copy link

stale bot commented Jan 8, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants