Selenium 4

[tcnh]

New Selenium 4 PR. (continues on base of #355)

Selenium 4.1.2 version
Relative locators
Shadow DOM access by using existing searchcontexts in Chromium 96+
DevTools Browsertest as a sample
ChromiumOptions for Chrome- and Edgedriver, with examples wiki page

Includes acceptance tests for shadowdom and relative locators

[fhoeben]

Haven't gone in full details yet, but looks pretty good.

Some global thoughts:

• should we add some documentation (references) to the top-level examples.BrowserTest.wiki for the new commands/features?
• the relative locators add a lot of new methods to the (already too big) BrowserTest class. And the require technical selectors (which you very nicely explicitly documented). Can we do something about that? I'm thinking whether it would be bad to have them in a separate subclass (I like that they are available, but think I would prefer tests that do not (need to) use them). Do you have any thoughts?

[tcnh]

Haven't gone in full details yet, but looks pretty good.

Some global thoughts:

• should we add some documentation (references) to the top-level examples.BrowserTest.wiki for the new commands/features?

I added them to the commands table (value of <> above/below/leftof/right of/near was missing, is added now)
I feel giving them much more acknowledgement would be to much credit for methods that should relatively not be used very often?

• the relative locators add a lot of new methods to the (already too big) BrowserTest class. And the require technical selectors (which you very nicely explicitly documented). Can we do something about that? I'm thinking whether it would be bad to have them in a separate subclass (I like that they are available, but think I would prefer tests that do not (need to) use them). Do you have any thoughts?

I agree (see above) that these are a bit of niche. On the other hand this is the most prominent addition to Selenium 4 for most end-users and I also believe there are a whole lot of methods in BrowserTest that are only used in specific use cases, so these are not that different. Splitting browsertest into multiple layers (of complexity/technology orientation/etc) might be a good idea, but as I mentioned, I believe we could move out a whole bunch of other methods and settings, too.

[fhoeben]

Maybe just a few links in the text above the table with BrowserTest commands to link to the new sample pages?