[QA] [E2] running and monitoring Echo and Flow browser tests

[Matthew Flaschen]

On 10/03/2014 01:46 PM, Jon Robson wrote:
> Would it be useful to send an email first thing Wednesday morning
> listing all the failing tests per project with links and how long they
> have been failing for.

Yes, definitely.

> I personally would find this sort of email useful to remind me to
> check status of code about to be merged.

Do you mean about to be cut into the new branch?

> On Thu, Sep 25, 2014 at 5:16 PM, Chris McMahon <cmcmahon at wikimedia.org> wrote:
[most text snipped out ... ]
>> My suggestions:
>>
>> * run the browser tests in a Vagrant env before you merge changes to master

Does this mean Jenkins automatically doing so as a voting pre-merge 
step?  That sounds great, if so.

Matt Flaschen