Skip to content
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

Pin the selenium-webdriver version so that it correctly matches protractor. #42

Closed
wants to merge 25 commits into from

Conversation

EricHeath-AI
Copy link

When the library versions differ at runtime you get strange test behaviour where the jasmine wrappers do not evaluate the control flow correctly.
More details here: angular/protractor#2790

hankduan and others added 24 commits January 5, 2015 12:32
Add some console logging, remove useless info about the last running
task in the control flow, and fix error where problems reported
from done.fail were getting pushed into the following spec.

Closes angular#18
Test wrapping for Jasmine 2 now more closely follows the test wrapping
for Mocha at https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/testing/index.js

This also adds more information to the task names in the control flow,
for easier debugging.
Note: this means that using `this.addMatchers` no longer works inside
before blocks or specs. It should have been changed to `jamsine.addMatchers`
since the upgrade to Jasmine 2. It was still working by accident up until
the previous commit.
Update selenium-webdriver to 2.47.0 from 2.45.1.
This update introduces a convoluted situation where some tests in
Proractor's suite would hang - see angular/protractor#2245

This change includes a fix for those issues which removes the explicit
`flow.execute` wrapper around `expect` calls. This appears not to introduce
any issues to existing tests.
… queue

Instead, expectations without promises in either expected or actual
are unchanged from the original Jasmine implementation.

See angular/protractor#2894
Latest selenium-webdriver no longer supports node 0.12.
Stop testing on it.
@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@EricHeath-AI
Copy link
Author

I signed it!

@googlebot
Copy link

CLAs look good, thanks!

@EricHeath-AI
Copy link
Author

I'm not sure what the build failure means here. Google closures were not happy with my change?

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

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.

7 participants