Skip to content
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
This repository was archived by the owner on Jul 29, 2024. It is now read-only.

selenium 4 upgrade process #4995

Closed
Closed
@cnishina

Description

@cnishina

The [email protected] upgrade process will be against the selenium4 branch. These will be code reviewed; however the tests might not pass.

change as much as possible without upgrading selenium-webdriver:

unforeseen steps (pushing out timeline by a week):

  • update internal runners
  • update internal test targets

also unforseen internal fixit week (pushing out timeline by another week):

copy over new selenium-webdriver typings to fix api calls:

  • fix protractor with new typing changes - 11/30 12/07 12/14
  • review changelog items from selenium4 - 11/30 12/07 12/14

upgrade selenium 4:

  • upgrade deps to selenium 4 (tests will probably fail) - 11/30 12/07 12/14
  • spend a magical amount of time hitting head against wall fixing things (if all goes well, maybe a week doing this) - 11/30 12/07 12/14

clean up:

  • move test suite to typescript - 12/07 12/14 12/21
  • light refactor with circle.yml file to .circleci folder - 12/07 12/14 12/21
  • look into bstack tests on travis failing (currently commented out)

wishlist:

  • remove extended webdriver js - 11/23 <-- this might not happen
  • maybe migrate over to webdriver-manager-replacement? or remove it from package.json - 12/21

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions