[QA] Where to run browser tests for multiple languages for Screenshots?

Amir E. Aharoni amir.aharoni at mail.huji.ac.il
Wed Jun 18 12:11:21 UTC 2014


2014-06-18 15:00 GMT+03:00 Antoine Musso <hashar+wmf at free.fr>:
> We only have a few wikis on the beta cluster because it is not strong
> enough to support the roughly 900 wikis WMF has in production.

We definitely don't need all 900.It's by language, not by project.

In practice, for this particular project and at this point in time, we
don't even need all languages, but only the languages into which the
feature in question is fully translated. The feature in question in at this
point VisualEditor, and there are 26 languages into which it has at least
95% translation. See
https://translatewiki.net/w/i.php?title=Special%3AMessageGroupStats&x=D&group=ext-visualeditor-0-all&suppressempty=1#sortable:3=desc

So what would seem good to me is to have a wiki for each of these 26
languages, and to add wikis as needed. Of course, it would be much more
robust for everybody if it would be an easy process to create such a wiki
in an automated scripted way - with the needed extensions, and with a bit
of imported content in the relevant language as well.

I'm trying to be forward-looking - given Wikimedia's massive
multilingualism it would be good to have an easy process for this.

> Have you thought of using the enwiki on beta and setting a different
> language ?  Appending &uselang=<some language code> might achieve the
> desired result.

This might be problematic. For example, for RTL languages, the content will
still appear as LTR, and for all languages, it will be good to have content
in the relevant language.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/qa/attachments/20140618/48a358a2/attachment.html>


More information about the QA mailing list