Skip to content

Upgrade Selenium Version#35949

Merged
TanayParikh merged 1 commit intomainfrom
taparik/upgradeSelenium
Aug 31, 2021
Merged

Upgrade Selenium Version#35949
TanayParikh merged 1 commit intomainfrom
taparik/upgradeSelenium

Conversation

@TanayParikh
Copy link
Copy Markdown
Contributor

Upgrading to latest stable selenium. The other two Selenium packages are already up to date.

@ghost ghost added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Aug 30, 2021
@TanayParikh TanayParikh marked this pull request as ready for review August 31, 2021 18:02
@TanayParikh TanayParikh requested a review from dougbu as a code owner August 31, 2021 18:02
@TanayParikh TanayParikh enabled auto-merge (squash) August 31, 2021 18:02
@TanayParikh TanayParikh requested a review from a team August 31, 2021 18:02
@TanayParikh TanayParikh disabled auto-merge August 31, 2021 18:03
Copy link
Copy Markdown
Contributor

@dougbu dougbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this works fine, please do the same in at least release/6.0.

Might be needed in our servicing branches too. But, let's wait until we hit problems there.

@TanayParikh
Copy link
Copy Markdown
Contributor Author

Verified the Selenium E2E tests are working with the updated driver locally (as they're no longer run via the CI)

@TanayParikh TanayParikh merged commit 2a254d0 into main Aug 31, 2021
@TanayParikh TanayParikh deleted the taparik/upgradeSelenium branch August 31, 2021 20:44
@ghost ghost added this to the 7.0-preview1 milestone Aug 31, 2021
TanayParikh added a commit that referenced this pull request Sep 1, 2021
TanayParikh added a commit that referenced this pull request Sep 1, 2021
@sebastienros
Copy link
Copy Markdown
Member

Verified the Selenium E2E tests are working with the updated driver locally (as they're no longer run via the CI)

Do you meant that a PR that would update these versions doesn't use the updated versions?
I can see the step in my PR:

#36107

image

@TanayParikh
Copy link
Copy Markdown
Contributor Author

I was referring to the src/Components/test/E2ETests specifically which use this selenium driver but are no longer run on the CI. This is different from the quarantined tests which as you noted are still on the CI.

@sebastienros
Copy link
Copy Markdown
Member

@TanayParikh
Copy link
Copy Markdown
Contributor Author

I believe those should be on 93 as well, don't see any reason why they would be intentionally a version behind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants