[Wikitech-l] Language features testing sprint (was Re: A testing & bug management wheel)

On 01/16/2013 02:25 PM, Quim Gil wrote: I just had a chat with Siebrand from the Language Engineering Team. They like the idea and they have specific proposals for all the weeks: http://etherpad.wikimedia.org/test-bug-i18n They are ready to start. Next week. So... why not? I will only look at the first week now (features testing). Their proposals are based on wiki pages that are pretty much ready for testers, even newcomers without much prior experience: Week 1: manual testing (Chris) * https://www.mediawiki.org/wiki/Milkshake/Manual_testing -- can be tested for each language. Reports to bugzilla. * https://www.mediawiki.org/wiki/VisualEditor/Typing/General -- can be tested for every language. Reports to bugzilla. * https://www.mediawiki.org/wiki/VisualEditor/Typing/Right-to-left -- can be tested for Hebrew. Needs one tester. Reports to bugzilla. * https://www.mediawiki.org/wiki/VisualEditor/Typing/Indic -- can be tested for all Indic languages with some adaptations. Only Hindi at the moment. VisualEditor looks like the primary goal, having Milkshake as secondary option for whoever feels more interested. The testing is aimed primarily to people with an interest in Hindi and Hebrew. Other Indic and RTL languages welcome. And in general non-Latin scripts. We have a nice pool of potential testers in the Wikipedias of those languages. Through ambassadors and community portals (and central notice? too soon/fast?) we could reach whoever we decide to reach. Of course we can do further outreach, but the Wikipedias alone should already provide the critical mass of contributors, right? Then we need to define the right environment for testing. Is it a fresh install in Labs? Something else? The wiki pages above already provide DIY testing cases. Together with https://www.mediawiki.org/wiki/How_to_report_a_bug we have the basics for the people willing to start contributing before the sprint. The sprint could be on Thursday, starting in Asian friendly times since this is where most of the potential testers will be based. We need to define if there is going to be a specific activity during the sprint, or if it's only a certain time-frame where full support will be provided to testers by the Language Engineering team. For instance, we could open the sprint with a hangout-screencast where someone goes briefly through the tests described. All the better if the demoers are a native Hindi speaker, a native Hebrew speaker, etc. There is potential for screencasts and chat rooms in those languages as well... I guess the goal would be to reach confidence in specific languages / scripts. If not confidence that it works well at least confidence that the issues are now reported as bugs. The incentive could be priority for Wikipedia in-your-language to be part of the next VisualEditor deployment: "Hi, we plan to deploy the next version of VisualEditor in your Wikipedia in two weeks, or as soon as we have the related documentation translated (link). The testing sprint some of the contributors of this Wikipedia made just gave us the confidence to include you in our Alpha deployment. Thank you everybody!" I think we can do it (with some adrenaline - good). -- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil