<div dir="ltr"><div>Hi Chris,<br></div><div><br></div><div>I did not go through all the test cases of Cirrus search. I went through the test cases for ULS both to understand how ULS works and to understand the feature files in cucumber. The testcases are easy to read and understand.</div>
<ul><li>I felt that the test cases could have more uniformity (if I have understood them correctly, that is). For instance, in uls_settings_panel.feature, we have the "input panel of language settings" and in uls_ime.feature, we have a "input box"..I think we are referring to the same thing here.</li>
<li>What is the interface language and what is the content language and how are these preferences set?</li><li>I executed the persistent_settings.feature manually. I did not understand the Background so I did not set these preferences. Just went ahead with the scenario. This scenario passes.But, when the font is changed to OpenDyslexic, then apply settings. Font changes to OpenDyslexic.Now, I change it back to System Font and apply settings, but it still remains OpenDyslexic instead of reverting to System Font (unless I log out and log back in).Is this expected behavior?</li>
</ul><div>Haven't concentrated on VisualEditor and not at all on Flow..but I will try/read about them. Instead of ULS, if I should focus on Cirrus search or Visual Editor, let me know.</div><div><br></div><div>-Renuka</div>
<div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Aug 29, 2013 at 3:56 PM, <span dir="ltr"><<a href="mailto:qa-request@lists.wikimedia.org" target="_blank">qa-request@lists.wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send QA mailing list submissions to<br>
<a href="mailto:qa@lists.wikimedia.org" target="_blank">qa@lists.wikimedia.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.wikimedia.org/mailman/listinfo/qa" target="_blank">https://lists.wikimedia.org/mailman/listinfo/qa</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:qa-request@lists.wikimedia.org" target="_blank">qa-request@lists.wikimedia.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:qa-owner@lists.wikimedia.org" target="_blank">qa-owner@lists.wikimedia.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of QA digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: QA Digest, Vol 4, Issue 23 (Chris McMahon)<br>
2. reminder: Tester's Guide to Software Development at WMF<br>
(Sumana Harihareswara)<br>
3. Re: Jenkins cleanup (Antoine Musso)<br>
4. Re: Visual Editor test plan (Chris McMahon)<br>
5. Re: Jenkins cleanup (James Forrester)<br>
6. Sep 18 workshop - Epic fail: figuring out Selenium test<br>
results (Quim Gil)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 29 Aug 2013 07:29:23 -0700<br>
From: Chris McMahon <<a href="mailto:christopher.mcmahon@gmail.com" target="_blank">christopher.mcmahon@gmail.com</a>><br>
To: "QA (software quality assurance) for Wikimedia projects."<br>
<<a href="mailto:qa@lists.wikimedia.org" target="_blank">qa@lists.wikimedia.org</a>><br>
Subject: Re: [QA] QA Digest, Vol 4, Issue 23<br>
Message-ID:<br>
<CAFBzvah3ZQeLd_uM00AjyaFXN_qGexyw=<a href="mailto:t3441aFWx9wGo932Q@mail.gmail.com" target="_blank">t3441aFWx9wGo932Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
On Wed, Aug 28, 2013 at 8:30 PM, Renuka Alurkar <<a href="mailto:renukaalurkar@gmail.com" target="_blank">renukaalurkar@gmail.com</a>>wrote:<br>
<br>
> Hi,<br>
><br>
> Zeljko, Thank you for approving my email.<br>
> Chris, Quilm Thank you for sending me other helpful links. I read about<br>
> manual features testing, browser testing using cucumber, and about saw the<br>
> video about the new tool article-feedback. I find both browser testing and<br>
> article feedback interesting. Well, I do not have any experience with<br>
> cucumber, but I would love to learn it through browser testing on<br>
> wikimedia. At the same time, I would like to test the article feedback tool<br>
> too.<br>
> I do not exactly remember how I came to know about how one could<br>
> contribute as a tester to wikipedia, but there is a possibility that I read<br>
> about it at<br>
> <a href="http://thesocialtester.co.uk/volunteering-a-good-way-to-learn-testing/" target="_blank">http://thesocialtester.co.uk/volunteering-a-good-way-to-learn-testing/</a> !!<br>
> Well, let me know how and when I can start!!!!!<br>
><br>
<br>
Hi Renuka,<br>
<br>
Article Feedback is an interesting feature, but unfortunately you are a bit<br>
late. AFT is no longer under active development and is only in use in some<br>
limited circumstances.<br>
<br>
Since you've read up a lot about what we do, let me suggest a few areas in<br>
which to concentrate:<br>
<br>
Our new search engine called "CirrusSearch" is available for testing right<br>
now on <a href="https://www.mediawiki.org" target="_blank">https://www.mediawiki.org</a> and <a href="http://en.wikipedia.beta.wmflabs.org/" target="_blank">http://en.wikipedia.beta.wmflabs.org/</a>.<br>
<br>
<br>
Some general notes about testing it are available at<br>
<a href="https://www.mediawiki.org/wiki/CirrusSearch" target="_blank">https://www.mediawiki.org/wiki/CirrusSearch</a>, and some previous mentions<br>
here on the QA list are at<br>
<a href="http://lists.wikimedia.org/pipermail/qa/2013-August/000354.html" target="_blank">http://lists.wikimedia.org/pipermail/qa/2013-August/000354.html</a> and<br>
<a href="http://lists.wikimedia.org/pipermail/qa/2013-August/000358.html" target="_blank">http://lists.wikimedia.org/pipermail/qa/2013-August/000358.html</a>. The<br>
automated tests we have may or may not be passing right now. They may not<br>
be too easy to read, but you can get an idea of what sort of thing we're<br>
testing for with them<br>
<a href="https://github.com/wikimedia/mediawiki-extensions-CirrusSearch/tree/master/tests/browser/features" target="_blank">https://github.com/wikimedia/mediawiki-extensions-CirrusSearch/tree/master/tests/browser/features</a><br>
.<br>
<br>
We'd like to hear what you think about the test we have and the testing we<br>
should have.<br>
<br>
The UniversalLanguageSelector (ULS) is a tool that allows users to<br>
manipulate the languages in which wikis appear. It is considered stable<br>
right now, but in the near future it will need to interact with our new<br>
VisualEditor. ULS is available in two ways: in the environment at<br>
<a href="http://en.wikipedia.beta.wmflabs.org/" target="_blank">http://en.wikipedia.beta.wmflabs.org/</a> it is represented as a "cog" icon<br>
(looks like a wheel) in the left-side "Languages" panel. In the<br>
environment at <a href="http://test2.wikipedia.org/" target="_blank">http://test2.wikipedia.org/</a> it is available as a link in the<br>
upper-right corner of each wiki page, and also as a small typewriter icon<br>
in every input box such as Search. The automated tests we have for ULS are<br>
<a href="https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector/tree/master/tests/browser/features" target="_blank">https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector/tree/master/tests/browser/features</a><br>
<br>
VisualEditor is our new WYSIWYG editor under development. It is available<br>
on every wiki, including in production on the English Wikipedia<br>
<a href="http://en.wikipedia.org/" target="_blank">http://en.wikipedia.org/</a>. (If you edit in production, do it on your user<br>
page or your user talk page, don't pollute real articles). As Amir noted<br>
earlier, some attention to non-Latin scripts in VE would be useful, as<br>
would an investigation of how cursor movements and such are working. Bugs<br>
in VE are very important right now. For now at least, the automated tests<br>
we have for VE are at<br>
<a href="https://github.com/wikimedia/mediawiki-extensions-VisualEditor/tree/master/modules/ve-mw/test/browser/features" target="_blank">https://github.com/wikimedia/mediawiki-extensions-VisualEditor/tree/master/modules/ve-mw/test/browser/features</a><br>
<br>
Finally, we are just beginning a big new feature called "Flow" that will be<br>
a new messaging system for the wikis. It is early enough in development<br>
that Flow is not implemented anywhere yet, but you can read about it at<br>
<a href="https://www.mediawiki.org/wiki/Flow" target="_blank">https://www.mediawiki.org/wiki/Flow</a> and you can watch for when it becomes<br>
available here: <a href="https://bugzilla.wikimedia.org/show_bug.cgi?id=53061" target="_blank">https://bugzilla.wikimedia.org/show_bug.cgi?id=53061</a><br>
<br>
-Chris<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wikimedia.org/pipermail/qa/attachments/20130829/fa5b3bd5/attachment-0001.html" target="_blank">http://lists.wikimedia.org/pipermail/qa/attachments/20130829/fa5b3bd5/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 29 Aug 2013 11:51:13 -0400<br>
From: Sumana Harihareswara <<a href="mailto:sumanah@wikimedia.org" target="_blank">sumanah@wikimedia.org</a>><br>
To: <a href="mailto:qa@lists.wikimedia.org" target="_blank">qa@lists.wikimedia.org</a><br>
Subject: [QA] reminder: Tester's Guide to Software Development at WMF<br>
Message-ID: <<a href="mailto:521F6DF1.1030609@wikimedia.org" target="_blank">521F6DF1.1030609@wikimedia.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
<a href="http://lists.wikimedia.org/pipermail/qa/2013-June/000021.html" target="_blank">http://lists.wikimedia.org/pipermail/qa/2013-June/000021.html</a><br>
"Tester's Guide to Software Development at WMF, circa June 2013"<br>
by Chris McMahon<br>
<br>
New folks might be interested in taking a look at this guide, in which<br>
Chris covers a few selected projects at WMF and talks about what they're<br>
up to. If that piques your interest and you'd like to know about other<br>
engineering projects at the Wikimedia Foundation, look at our most<br>
recent monthly engineering report:<br>
<a href="https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/July" target="_blank">https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/July</a><br>
--<br>
Sumana Harihareswara<br>
Engineering Community Manager<br>
Wikimedia Foundation<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 29 Aug 2013 18:20:06 +0200<br>
From: Antoine Musso <<a href="mailto:hashar%2Bwmf@free.fr" target="_blank">hashar+wmf@free.fr</a>><br>
To: <a href="mailto:qa@lists.wikimedia.org" target="_blank">qa@lists.wikimedia.org</a><br>
Subject: Re: [QA] Jenkins cleanup<br>
Message-ID: <kvnsbe$kae$<a href="mailto:1@ger.gmane.org" target="_blank">1@ger.gmane.org</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Le 27/08/13 13:03, Željko Filipin a écrit :<br>
> This is actually a Big Thing. ULS is the third repository that has<br>
> Selenium tests. This is the complete list:<br>
><br>
> <a href="https://github.com/wikimedia/mediawiki-extensions-CirrusSearch" target="_blank">https://github.com/wikimedia/mediawiki-extensions-CirrusSearch</a><br>
> <a href="https://github.com/wikimedia/mediawiki-extensions-MobileFrontend" target="_blank">https://github.com/wikimedia/mediawiki-extensions-MobileFrontend</a><br>
> <a href="https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector" target="_blank">https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector</a><br>
><br>
> The tests are in folder tests/browser or tests/acceptance.<br>
<br>
Next thing would be to have the Selenium tests run whenever someone send<br>
a change in Gerrit :-]<br>
<br>
We talked about it with Željko on IRC, we might want to sprint that soon<br>
<br>
--<br>
Antoine "hashar" Musso<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 29 Aug 2013 09:21:17 -0700<br>
From: Chris McMahon <<a href="mailto:cmcmahon@wikimedia.org" target="_blank">cmcmahon@wikimedia.org</a>><br>
To: "QA (software quality assurance) for Wikimedia projects."<br>
<<a href="mailto:qa@lists.wikimedia.org" target="_blank">qa@lists.wikimedia.org</a>><br>
Subject: Re: [QA] Visual Editor test plan<br>
Message-ID:<br>
<<a href="mailto:CAJohBHTR68LvxBKOKZZ7c2p2SePw6E-_oCcojaKv4VHmTbLjjw@mail.gmail.com" target="_blank">CAJohBHTR68LvxBKOKZZ7c2p2SePw6E-_oCcojaKv4VHmTbLjjw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Thu, Aug 29, 2013 at 6:13 AM, Željko Filipin <<a href="mailto:zfilipin@wikimedia.org" target="_blank">zfilipin@wikimedia.org</a>>wrote:<br>
<br>
> On Tue, Aug 27, 2013 at 9:40 PM, Rachel Thomas <<a href="mailto:rachelqa99@gmail.com" target="_blank">rachelqa99@gmail.com</a>>wrote:<br>
><br>
>> I was wondering if there is also a standard place we should keep test<br>
>> plans. I'm not sure what is currently being done for test plans.<br>
><br>
><br>
> Chris will probably know more, but I do not think we have a standard<br>
> place. Well, <a href="http://mediawiki.org" target="_blank">mediawiki.org</a> is probably the standard place, but that is<br>
> probably now what you were looking for. :)<br>
><br>
<br>
I think it depends on the context. The test plans I have written in the<br>
past have had some relationship to the project being tested or to the test<br>
event. Rachel's test plan for VE is I think appropriate for the OPW<br>
project. As long as it is findable and linkable on for example<br>
<a href="http://mediawiki.org" target="_blank">mediawiki.org</a>, it's all good.<br>
-Chris<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wikimedia.org/pipermail/qa/attachments/20130829/7231e975/attachment-0001.html" target="_blank">http://lists.wikimedia.org/pipermail/qa/attachments/20130829/7231e975/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Thu, 29 Aug 2013 12:06:14 -0700<br>
From: James Forrester <<a href="mailto:jforrester@wikimedia.org" target="_blank">jforrester@wikimedia.org</a>><br>
To: "QA (software quality assurance) for Wikimedia projects."<br>
<<a href="mailto:qa@lists.wikimedia.org" target="_blank">qa@lists.wikimedia.org</a>><br>
Subject: Re: [QA] Jenkins cleanup<br>
Message-ID:<br>
<<a href="mailto:CAEWGtDW6SwaMYCg5ia9OiB04Xi5pbxoXAysXYtJ3BwOGwumCNg@mail.gmail.com" target="_blank">CAEWGtDW6SwaMYCg5ia9OiB04Xi5pbxoXAysXYtJ3BwOGwumCNg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On 29 August 2013 06:52, Rachel Thomas <<a href="mailto:rachelqa99@gmail.com" target="_blank">rachelqa99@gmail.com</a>> wrote:<br>
<br>
> James- I'm still working on some tests for Visual Editor now. I'm<br>
> currently testing the bullets, numbering, indents and outdents. Maybe I<br>
> should try and coordinate with your team regarding what tests I have done<br>
> already and what I should do next? I'm not sure what the plan is for the<br>
> VE repo or the VE tests, but I think it would be worth discussing it with<br>
> you, Chris and Zeljko, and perhaps members of your team, as I have seen<br>
> some conflicting information.<br>
><br>
<br>
That'd be really great, yes. Right now our "pain areas" are reliably<br>
inserting and deleting text in paragraphs and lists, splitting them, and<br>
copy-pasting them, in "complex" scripts (non-latin and non-Cyrillic,<br>
mostly). Some of this starts to touch on native- and ULS-based Input Method<br>
Editors, which are terribly complex (and horrible to test), but getting a<br>
start would be great.<br>
<br>
J.<br>
--<br>
James D. Forrester<br>
Product Manager, VisualEditor<br>
Wikimedia Foundation, Inc.<br>
<br>
<a href="mailto:jforrester@wikimedia.org" target="_blank">jforrester@wikimedia.org</a> | @jdforrester<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wikimedia.org/pipermail/qa/attachments/20130829/82ffc4b4/attachment-0001.html" target="_blank">http://lists.wikimedia.org/pipermail/qa/attachments/20130829/82ffc4b4/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Thu, 29 Aug 2013 13:56:25 -0700<br>
From: Quim Gil <<a href="mailto:qgil@wikimedia.org" target="_blank">qgil@wikimedia.org</a>><br>
To: <a href="mailto:qa@lists.wikimedia.org" target="_blank">qa@lists.wikimedia.org</a><br>
Subject: [QA] Sep 18 workshop - Epic fail: figuring out Selenium test<br>
results<br>
Message-ID: <<a href="mailto:521FB579.2090104@wikimedia.org" target="_blank">521FB579.2090104@wikimedia.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
It's official!<br>
<br>
Epic fail: figuring out Selenium test results<br>
<a href="http://www.meetup.com/wikimedia-tech/events/137381022/" target="_blank">http://www.meetup.com/wikimedia-tech/events/137381022/</a><br>
<br>
--<br>
Quim Gil<br>
Technical Contributor Coordinator @ Wikimedia Foundation<br>
<a href="http://www.mediawiki.org/wiki/User:Qgil" target="_blank">http://www.mediawiki.org/wiki/User:Qgil</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
QA mailing list<br>
<a href="mailto:QA@lists.wikimedia.org" target="_blank">QA@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/qa" target="_blank">https://lists.wikimedia.org/mailman/listinfo/qa</a><br>
<br>
<br>
End of QA Digest, Vol 4, Issue 27<br>
*********************************<br>
</blockquote></div><br></div></div>