Skip to content

Update Selenium to 4.8 and 109 #46423

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

Merged
merged 1 commit into from
Feb 2, 2023
Merged

Conversation

Tratcher
Copy link
Member

@Tratcher Tratcher commented Feb 2, 2023

This is a routine monthly update (hopefully)

@Tratcher Tratcher requested review from a team, dougbu and wtgodbe as code owners February 2, 2023 20:53
@Tratcher Tratcher self-assigned this Feb 2, 2023
Copy link
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.

🤞

@halter73
Copy link
Member

halter73 commented Feb 2, 2023

It looks like the only test that still uses Selenium rather than Playwright, ChromeTests.Http2(), has been completely skipped for a while. The Wasm.Performance benchmarks also use it, but we don't test that as part of PR builds, do we? I think we'd only catch compilation failures. Am I missing something?

@halter73
Copy link
Member

halter73 commented Feb 2, 2023

Never mind. I was missing E2ETesting.props.

@Tratcher Tratcher merged commit 7976429 into dotnet:main Feb 2, 2023
@Tratcher Tratcher deleted the tratcher/selenium branch February 2, 2023 22:47
@ghost ghost added this to the 8.0-preview2 milestone Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants