-
Notifications
You must be signed in to change notification settings - Fork 18
Migrate to SeleniumHQ 3 #11
Comments
ad 1. I can update them. When will I be sure that everything works? When the code compiles and the SampleUITest tests are passing? ad 2. Should it be done similar to #20 ? |
I have created a bug #21 that covers updating to geckodriver. The are separate think (geckodriver and Selenium 3), so separate issues are better, @cezarypiatek what do you think? |
Ad1. I have a private set of tests (over a 300 assertions) When I run this suit and everything will be ok then I'll accept your PR. Ad2. Please extend script for downloading drivers. Nuget packages should be an alternative (there is no OFFICIAL nuget package with given driver) |
- Update selenium to 3.4 - Update drivers - Fix filtering covered endpoints
- Fix selenium version in nuspect
- Add ScrollIntoViewIfNotVisible
According do geckodriver issue tracker (https://github.com/mozilla/geckodriver/issues) there is a lot issues related to clicking and typing (SenKeys) so I'm still not convinced about migration to Selenium 3.X |
I fully understand that. |
- Update selenium version - Introduce geckodiver BrowserType
- remove reference to driver binary
I've created branch SeleniumHQ_3_5 with Selenium 3.6. There has been introduced two BrowserTypes related to Firefox:
This is necessary because Geckodriver has issues with clicking what makes impossible to create stable UI tests. It also does not support full page screenshots what makes VisualAssertion useless. |
- Update selenium version - Introduce geckodiver BrowserType
- remove reference to driver binary
The text was updated successfully, but these errors were encountered: