W3C Driver todo:

- decide the default we run @ CI (maybe a mix?). Both about selenium y/n and headless y/n
- moodle.docker support for this
- moodle-plugin-ci support for this.
- show some example profiles and config.
- mobile, workplace...
- details about needed dirvers (chromedriver, geckodirver...), links to them...
- update behat related pages in docs... specially selenium-less combos (and how to launch the browsers)
- shared with Andrew: consider renaming the "gecko" profile to "geckodriver" (same for headless), for consistency with other "direct" profiles (like chromedriver and edgedriver).
- document how to run the "no-selenium" versions (launche the xxxdriver manually). it's not specified anywhere (that I've found).
- document restrictions (for example parallel runs with firefox in the same session and things like that). Maybe a matrix can be done, showing what works and what doesn't (maybe that's too much if exceptions are only a few).
- Update the browsers, selenium and drivers versions page in the docs (waiting for chromedriver/chrome 89)
- Remind people that not old behat.yml file can be @ Moodle's dirroot, it can lead to errors beacuse of incompatibility of extension names. Remove it.
- Under windows, if the corresponding driver is not running (chromedriver, geckodriver, edgedriver, selenium) is not running, you don't get any error, the behat execution just ends and done. With linux, mac there is a visible error.
- Unabe to run edgedriver, neither with mac (missing libc++ library) or windows (apparently followed all the steps, used correct webdriver version, had developer tools enabled... but no luck).


Q:

- Do all them support screenshots? w/wo selenium head and headless,
- why there are only 3 "edge" profiles, no headless edge with selenium ?