We should make sure all code hitting the MediaWiki deployment train is good and all our tests are passing every Monday. Not sure how to automate this but we could always do this manually.
|Resolved||zeljkofilipin||T91669 Make browser tests voting for all repos of WMF deployed code|
|Resolved||zeljkofilipin||T55697 [EPIC] trigger browser tests from Gerrit (tracking)|
|Resolved||Jhernandez||T104315 [GOAL]: Set up testing environments that run browser tests on all patches.|
|Resolved||Jdlrobson||T100293 [EPIC] Run browser tests against every MobileFrontend/Gather patch|
|Duplicate||phuedx||T101865 Ensure tests are green before they hit production|
|Resolved||Jdlrobson||T108973 Spike: How do we ensure tests are green before they hit production?|
Jenkins can run planned jobs, too, so maybe Unit (and browser?) tests can run in the night so you can evaluate the results on monday?
 In general, i'm not sure, if it's possible in wmf setup, but I think so :)
@greg is this something that release engineering could organised?
I'm imagining an e-mail sent at time of branch cut reporting all the tests that are failing organisation wide pre-deployment. I assume there is a window between branch cut and deploying to production that could be utilised to make quick regression fixes.
It would be a great way to increase visibility of failing tests....