<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I think it'd be pretty heavy to run it per language and you'd have to have a good place to run it per language but eying that you could run it headless if you like. The screenshot API the tests hvw access to is petty good. It'll snap either the whole screen or just a part of it and you can call it any time you like in the test. No sauce required. <br><br>Sent from my iPhone</div><div><br>On Feb 15, 2014, at 1:27 PM, "Amir E. Aharoni" <<a href="mailto:amir.aharoni@mail.huji.ac.il">amir.aharoni@mail.huji.ac.il</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="rtl"><div dir="ltr">Hi,<br><br></div><div dir="ltr">There's something that bothered me for a while about VisualEditor, and essentially it can be said about any other user-facing component that we are developing: If we are writing a user manual, such as <a href="https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide">https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide</a> , we want to get it translated to as many languages as possible to be useful to all people. It's quite easy to do with the Translate extension, but how do we translate the screenshots?<br>
<br></div><div dir="ltr">It's possible (though not trivial) to make a custom file name for each language, but this still leaves the question of how will the screenshots be created and updated when the developers change the UI.<br>
<br></div><div dir="ltr">And now it suddenly struck me: Can we use our tests for that? To do something like this:<br>1. Write test scenarios that run the features described in the user manual.<br>2. Run these scenarios on all the languages that we support (or at least on a large set, say fifty languages).<br>
</div><div dir="ltr">3. Get the screenshots that are create in SauceLabs, and save them with a suffix of a language code in the file name.<br></div><div dir="ltr">4. Upload them automatically to Commons.<br></div><div dir="ltr">
5. Profit: Truly localized user manuals.<br></div><div dir="ltr">6. Profit 2: Truly multilingual tests.<br><br>Maybe we don't even have to run this job regularly, if it's too heavy. It will probably be enough to do it once every couple of weeks or simply by demand, when a feature clearly changes.<br>
<br></div><div dir="ltr">Is this crazy talk? Or can it scale?<br clear="all"></div><div><div><br>--<br>Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי<br><a href="http://aharoni.wordpress.com" target="_blank">http://aharoni.wordpress.com</a><br>
“We're living in pieces,<br>I want to live in peace.” – T. Moore</div>
</div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>QA mailing list</span><br><span><a href="mailto:QA@lists.wikimedia.org">QA@lists.wikimedia.org</a></span><br><span><a href="https://lists.wikimedia.org/mailman/listinfo/qa">https://lists.wikimedia.org/mailman/listinfo/qa</a></span><br></div></blockquote></body></html>