See https://lists.wikimedia.org/pipermail/wikitech-l/2015-September/083057.html
The Jenkins Job:
Let's get these browser tests running per commit.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| 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 | zeljkofilipin | T111467 Run browser tests in core on every commit |
The MediaWiki core PHPUnit Zend tests are taking 10 minutes. So if the browser test jobs takes less than 10 mins its i not going to cause any slowness in gating.
On patchset proposal, the slowest is PHPUnit HHVM which takes roughly 5 minutes. Jon pointed a job in the task description which 7-8 minutes but uses SauceLabs. Targeting a local browser/site would definitely be faster.
At worth, we can play with it in Zuul experimental pipeline first then generalize :}
Currently we have a mwext-selenium job which is generic for extensions. Will "just" have to adapt it for mw/core.