This is a sub project of bug 53697 https://www.mediawiki.org/wiki/Continuous_integration/Browser_tests
It covers setting up the Zuul configuration to trigger browser tests. From the wiki page:
The exact workflow would need to be figured out with the VisualEditor team. A first step would be to run the browser tests after a change has been merged and report back in Gerrit for their information.
At first we will only want to run browser tests after a change has been merged. This let us load the system progressively without disrupting the VisualEditor authors.
We can later on make Zuul report back in Gerrit a message stating the result of the tests, that will raise awareness among developers and they can work on fixing the unsuccessful tests. Additionally, we can have the browser tests to be triggered on every patchset, the labs instance load will have to be carefully monitored.
Once tests are properly passing and the setup has been proven useful, we can make Zuul to block patchsets not passing the browser tests. The developers would then be required to fix the code or the test to have their change merged in