[05:57:13] <florent>	 kindrobot: About the e2e tests, may we set the tests headless by default and enable the browser window to appear only when an option is enable? It would be more practical I guess to run them locally
[07:01:49] <florent>	 I proposed a PR for that, with the hope it will improve discorability of this option: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikiLambda/+/854873
[07:01:49] <florent>	 I won't mind if you disagree and close the PR though, that's not something I care much about
[16:29:26] <kindrobot>	 Thanks for bringing that up florent. I'll check with Zelko on the QTE team to see if there's an expectation that they run one way or another. I imagine they run headless in CI anyways.
[16:34:42] <kindrobot>	 Zelko, for context, is the primary maintainer of the Selenium browser testing tooling.
[17:29:11] <florent>	 Oh, OK !
[17:30:59] <florent>	 Yeah, it seems like it is for the CI, but I wonder why an option other than a variable environment (`DISPLAY` on Linux being a special one) is offered. My usual way of testing is to disable headless only for debuging the tests.
[18:28:08] <James_F>	 florent: Our CI jobs run on the 'quibble' docker images which are defined at https://gerrit.wikimedia.org/r/plugins/gitiles/integration/config/+/refs/heads/master/dockerfiles/quibble-buster/Dockerfile.template#99 for the browsers/drivers specifically (and other places). We use xvfb so that (I believe) it's as realistic as possible.