-
Notifications
You must be signed in to change notification settings - Fork 142
chore: run e2e tests on saucelabs #135
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
Conversation
vigneshshanmugam
commented
Dec 24, 2018
- Getting rid of selenium and running the e2e tests on sauce labs instead.
9c203f2
to
a7ff833
Compare
Thanks @vigneshshanmugam! Would you please take a look at the failing tests as well? |
@jahtalab IE 11 has some weird timeout issues on scripts.. More details - angular/protractor#1999 I am trying to find how we can run on 32 bit version instead. |
d426a25
to
fc14b1f
Compare
@jahtalab I have disabled IE test for now because of the executeAsync issue, I have tried both 32 and 64 bit drivers and it works when running the script locally but fails through travis..Even increasing the timeout did not help.. |
Thanks @vigneshshanmugam , looks good 👍 |
* chore: run e2e tests on saucelabs * remove headless chrome & firefox * disable unit tests in karma * increase timeout on node tests * comment changes * few changes for saucelabs proxy * add all browsers to test * run only in chrome and firefox as before * only log in chrome * pass tunnel id to capabilities * remove after test hook - testing firefox * fix logs command issue * make e2e tests work in IE 11 * check fetch support on IE * set max instances to 1 for chrome * move back to max instances - 1 * change server port to 8003 * change apm server url * change windows 8.1 * run on ie driver version 2.48 * enable fetch in test * fix fetch url and ignore IE 11 * update addons in travis * force 64 bit driver on IE * run unit tests and disable IE