[QA] A browser test challenge

[Rachel Thomas]

Sure, I can do maintenance on the existing tests. Sounds like you are
talking about the browsertests repo, so I will start there first.

--Rachel



On Wed, Oct 9, 2013 at 9:49 AM, Chris McMahon <cmcmahon at wikimedia.org>wrote:

>
>
>
>
> On Tue, Oct 8, 2013 at 11:40 AM, Rachel Thomas <rachelqa99 at gmail.com>wrote:
>
>> Hi Chris/Zeljko,
>>
>> I am thinking of writing a test for Twinkle, as it seems to be one of the
>> more popular gadgets.  What are your thoughts on my testing of that one?
>>
>
> Hi Rachel,
>
> Since you have some pretty good experience with our suites, what would you
> think about doing some maintenance on the existing tests?  For example, the
> build for Firefox on beta labs was all green Oct 1 but now has 10 failures.
>  I'm looking at the test for search right now, I'm guessing an identifier
> has changed.
>
> But we have some perplexing differences with e.g. the Print/export
> expand/collapse tests on beta and test2.  I reported
> https://bugzilla.wikimedia.org/show_bug.cgi?id=54886 but I'm not sure
> that's all of the issue.
>
> Since we've moved the suites into the repos for their extensions (VE, ULS,
> CirrusSearch, Flow soon), we are working on moving all the shared code into
> a single gem.  It would be great to have the tests green (or mostly green)
> before we deploy that big change, so we can tell where the problems might
> be more easily.
>
>
>>
>>
> _______________________________________________
> QA mailing list
> QA at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/qa
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/qa/attachments/20131009/d505425e/attachment.html>