Update selenium version

[JunTaoLuo]

Part of https://github.com/dotnet/aspnetcore-internal/issues/3777

I'm hoping we can move to using Playwright asap so we don't have to make these types of changes.

[dougbu]

@javiercn I don't see anything using the $(Selenium*) properties. Did you leave them behind for a reason❔ If not, can anything else from our Selenium history that could be deleted❔

@JunTaoLuo I suggest repurposing this PR to remove the $(Selenium*) properties and whatever else @javiercn says can go.

Please also update the ops rotation docs and issue template. @javiercn should something be done with the $(Playwright*) properties on a regular basis❔

[JunTaoLuo]

I was wondering about that since I still see Selenium used in https://github.com/dotnet/aspnetcore/blob/main/src/Servers/Kestrel/test/Interop.FunctionalTests/Interop.FunctionalTests.csproj#L27-L28. I think only the blazor template tests and some other tests have been converted to using Playwright, not the entire repo.

[javiercn]

@dougbu Components still uses Selenium.

[dougbu]

More generally, any changes expecting to grab new versions from NuGet must be coordinated with @mmitche, @wtgodbe, or DncEng. Must get the new packages into the dotnet-public feed prior to submitting PRs like this one.

[JunTaoLuo]

Yup, I just remembered we don't get packages from NuGet directly.

[dougbu]

Ah, my bad on thinking the properties should be removed. Do we also need to get new Playwrite versions❔

[javiercn]

@dougbu to a Degree, but we are still figuring out how often we want to update.

Playwright releases at the same cadence as Chrome, but a given version targets a fixed version of Chrom(ium) so as long as we don't stay behind for a year we are likely ok. We can always target a new browser version with an older driver, but compatibility is not guaranteed in that case.

[JunTaoLuo]

I think that was the rationale for us to upgrade Selenium versions as part of Ops rotation. It's a preventative measure so that we are not blindsided by any chrome/driver incompatibilities. Is there harm in updating too frequently @javiercn ?

[dougbu]

It's a preventative measure so that we are not blindsided by any chrome/driver incompatibilities.

Agreed. We don't have control over the Chrome version eng\scripts\InstallGoogleChrome.ps1 installs because the download URI is not version-specific.

[javiercn]

Agreed. We don't have control over the Chrome version eng\scripts\InstallGoogleChrome.ps1 installs because the download URI is not version-specific.

Chrome doesn't offer version specific stuff for these things, once a new version is out is "impossible" to download the older version bits (I tried at some point).

[ghost]

Hello @JunTaoLuo!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[JunTaoLuo]

FYI, I'll edit the doc to include updating Playwright when this PR passes.

[JunTaoLuo]

Hmmm there was a complication with the playwright version update complaining that the driver executable can’t be found. I’ve reverted that to unblock the selenium update.