-
Notifications
You must be signed in to change notification settings - Fork 9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Travis build is broken with selenium-webdriver tests. #1773
Comments
Looks like I've narrowed it down to swagger-client@2.1.7 |
So... the fix is not so simple... |
A possible workaround is to force a downgrade of |
Eww yes we can go to 3.4.3 in js if we can verify that it works |
I've tested locally
PS: this didn't just break the tests. It broke Swagger-UI. I tested the above by serving up swagger-ui, as well with Chrome 46 and firefox (?) swagger-ui@master ( with swagger-client@2.1.7 ) , built on node.js <= 0.12.x would produce a browser error and stall. |
how could it break swagger-ui? there is no node process in the runtime of that, unless it's causing it to build incorrectly. |
at build time, it adds the erroneous module to it. TLDR; To repeat...
|
Hi All, I am trying to Automate Swagger using selenium. Seleinium is not able to identify the elements, Please let me know what are the setup's required to do. |
I imagine you might need to wait for the javascript to render the page first. Once its loaded, you can use any old selector to find the elements. |
By some magic, if I build with node.js 4.2.2 the tests run. If I build with 0.10 (as travis is configured to) it fails.
Initially I thought this was related to browserify, but swagger-ui just concats its files!
The text was updated successfully, but these errors were encountered: