Just so people know which repos I am looking at : I am going to start by looking at this one: VisualEditor-test2.wikipedia.org-linux-firefox which has been failing for the past 6 days. After that, I would like to look at Cirrus Search repo.
Thanks. --Rachel On Thu, Oct 10, 2013 at 9:54 AM, Chris McMahon <[email protected]>wrote: > > > > On Thu, Oct 10, 2013 at 3:28 AM, Željko Filipin <[email protected]>wrote: > >> On Wed, Oct 9, 2013 at 8:23 PM, Rachel Thomas <[email protected]>wrote: >> >>> Sure, I can do maintenance on the existing tests. Sounds like you are >>> talking about the browsertests repo, so I will start there first. >> >> >> You can start anywhere, we have plenty of failed tests in almost any >> repository. :) >> >> The teams in charge of repositories are starting to work on keeping the >> tests green in their repositories, but since almost everybody is new to >> browser automation, they all do need help. >> > > And of course look for bugs! We have some important open bugs and recent > bugs right now found because of browser test failures: > > https://bugzilla.wikimedia.org/show_bug.cgi?id=54886 we are discussing > today whether to revert these changes or fix the expand/collapse navigation > properly. > https://bugzilla.wikimedia.org/show_bug.cgi?id=54977 (CLOSED) caught > immediately in beta labs, caused VisualEditor to fail completely > https://bugzilla.wikimedia.org/show_bug.cgi?id=54977 (BELIEVE FIXED, > NEEDS CHECKING) causes intermittent VE failures in Chrome, unpleasant user > experience > > and more to come I am sure. > -Chris > > > _______________________________________________ > QA mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/qa > >
_______________________________________________ QA mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/qa
