-
Notifications
You must be signed in to change notification settings - Fork 230
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
Update e2e test dependency updates & get them running on Mac #2083
Update e2e test dependency updates & get them running on Mac #2083
Conversation
@benjaminapetersen 👍 nice work |
@stevekuznetsov I may request some assistance from you here as well soon. Working on the other PR I pinged you on first as unit tests should be easier than e2e to get up and running again... |
43e9fd2
to
e553d83
Compare
Been working on getting some progress with angular/webdriver-manager#270 I don't see much activity in |
e553d83
to
41ffaeb
Compare
e61b45f
to
2897413
Compare
[test] |
1 similar comment
[test] |
Sigh. Welp, twas' working a week ago. Wheee! Tempted to suggest converting e2e tests to unit tests & dropping the whole e2e flow entirely.... |
Issue in protractor tracking one of our problems. Our chrome-driver dependency is not latest, so we are getting a bug (see the convo), however, second issue where protractor is incorrectly seeing both capabilities & multiCapabilities. |
issue in webdriver manager tracking one of our problems. |
[test] plz |
Issues:
🙁 |
lolz... welp, runs locally, won't run in travis. flipped the problem around now. 🙄 |
[test] |
1 similar comment
[test] |
@benjaminapetersen I think you need to get screenshots working again to be able to debug in Jenkins. |
[test] |
1 similar comment
[test] |
yay screenshots |
/retest |
Attempting to work out the flakes running the tests in CI. Opened an issue with Hawtio as the manual bootstrapping (on the document) may be causing some of the issue: Hawtio 2398 and manual bootstrap instructions. Also, angular.bootstrap function docs page states:
|
/test |
Hi, just cloned this PR branch and after upgrading my Chrome browser (linux/Fedora v62), e2e tests passed. |
Great, thanks @dtaylor113. So far then, @benjaminapetersen, @dtaylor113 & @rhamilto have run successfully, but @spadgett has not been able to get them to run. CI is currently flaky, but I'm pretty sure I know why & will try to address that today if possible. |
/test |
Jenkins / Travis success. /test again (going for 3x) |
@stevekuznetsov 😠 😡 😠 😡 |
/retest |
- Upgrade protractor & dependencies - Rewrite tests to match new APIs - Remove deprecated tests - Remove protractor-mac.conf.js & use a single protractor config - Add `user logs in` spec to work out bugs with the login flow. - Fix login flow (non-angular page), update some helpers to new protractor apis, fixing individual tests in progress - Add temp e2e grunt task to make testing quicker - Add additional scrollTo window helpers - Update createFromTemplate page to eliminate test flakes due to protractor changes - Add nextSteps page pageObject - Remove chrome from multiCapabilities in protractor.conf so grunt can handle setting the browser - Update framework from jasmine to jasmine2 in protractor.conf.js - Deduplicate common setup across test suites - Add implicit browser.wait(1000) every time new PageObject() or PageObject.visit() to ensure items are properly rendered before tests continue - Update support for screenshots. Screenshots will be saved in /test/tmp/<browser>/<spec_title>.png - Screenshots taken for failed tests only - Add new user_creates_project e2e test that exercises our menus (rather than browser page refreshes) - Always default protractor to run with Chrome - Standardize timing across modules - Improve reporting output of protractor tests - Use color output locally on mac for test output, plain text in Jenkins - Jenkins does not do well with the escape codes - Prow (Jenkins) should now use the JUnit xml files to give us better context on failure anyway
8d81f24
to
75fd47b
Compare
rebased, happily was not painful. |
@benjaminapetersen: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@benjaminapetersen PR needs rebase |
Revisited this, and got over the
Doesn't look like the protractor team is going to address that anytime soon. Its still usable, but its a |
I think we'd see that node 8 error without these changes. That seems to just be a protractor problem. |
Yup, its just general.... just a little concerned the protractor & webdriver-manager teams are not terribly responsive anymore. |
https://trello.com/c/w3vdwj85
fix #2200
Based off of #2068, though not really dependent. Related to #1473, a previous attempt at getting our e2e tests running.
Depends on #2268 for junit additions.
NOTE: this PR currently contains a backup of
node_modules/protractor
intest/package_backups/protractor
, which accounts for many of the listed files changed (166!)TODO:
.conf.js
fileshelpers/nonAngular.js
Get e2e tests running locally in FirefoxGet e2e tests running in PhantomJS or NightmareISSUES:
Accepting certs does not work in Firefox(now using chrome)Need to run(not with chrome)grunt serve
once in order to accept certsWebdriver manager is a huge hassle due to a dependence on Github's API, which is aggressively rate-limited when non-authenticated. It attempts to use the API to detect a good Selenium server to download.(appears to have resolved on its own, unfortunately I think these dependencies can change under us)npm install
works fine outside of the office, but in office the rate-limit is always exceeded (IP address specific I suppose). This is a known issue, links in comments below.Firefox ESR download links for testing locally (match jenkins):
(this PR/branch will not work with these verisons of FF, but our current setup with Protractor 1.x should work)
For reference, Downgrade of FF in Jenkins PR
For reference, jenkins config file
@spadgett