Incorrect guidelines for selenium test automation #7184
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
rogerwang
reviewed
Oct 28, 2019
| @@ -15,8 +15,7 @@ The following workflow uses [selenium-python](http://selenium-python.readthedocs | |||
|
|
|||
| ### 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. | |||
There was a problem hiding this comment.
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.
|
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.