[QA] [WikimediaMobile] Failing MobileFrontend browser tests

[Juliusz Gonera]

I think Arthur found the right words to describe what the problem is
for us. If "we're not there yet" then we should disable all browser
test notifications altogether because there's no point in getting
several emails about failing tests on mobile-tech if we know they will
be for sure failing.

On Thu, Jul 10, 2014 at 1:38 PM, Arthur Richards
<arichards at wikimedia.org> wrote:
> Thanks for the replies, everyone - however I haven't seen Antoine's response
> (beyond the bit quoted in Chris Steipp's reply), did it not get reply all'd
> or otherwise not sent to mobile-l? Further response inline.
>
> On Thu, Jul 10, 2014 at 12:06 PM, Rob Lanphier <robla at wikimedia.org> wrote:
>>
>> Antoine and Zeljko are the right people to talk about this while Chris is
>> out, and it's late in the day for them.  I'm sure they'll get back to you
>> tomorrow.  Greg may be able to say more about this, but honestly, the nature
>> of this thread is a little bit like little kids in the backseat saying "are
>> we there yet? are we there yet?" repeatedly  :-)
>
>
> Rob, the last time we inquired about this (to my knowledge) was one month
> ago (see email subject 'migrating MobileFrontend browser tests to WMF
> Jenkins'). We saw no substantive followup, and our browser test builds have
> been broken since the migration over one month ago as a result of
> infrastructural issues. This not only rendered the automated browser tests
> essentially useless for us but it has also become a significant drain on
> time and focus. This isn't a case of us asking 'are we there yet' - rather
> it's a case of us trying to understand when we'll be able to rely on our
> browser tests again and to see if there's any way we can help to improve the
> situation.
>
> --
> Arthur Richards
> Team Practices Lead
> [[User:Awjrichards]]
> IRC: awjr
> +1-415-839-6885 x6687