[QA] QA Digest, Vol 5, Issue 1 (ULS)

Thu Sep 5 20:31:50 UTC 2013

Hi Chris,

Sorry for a late reply..I have been unsuccessfully trying to install
Cygwin,Ruby, Cucumber on my system, still not done with it.
The scenario I had mentioned was closer to bug 52571. I executed my steps
and a couple of bugs multiple times, and now I am unable to reproduce what
I had mentioned in my previous email :(

Here is another scenario:

1) Click cog
2)Click Display
3)Change font ( say, from SystemFont to OpenDyslexic)
Observed and Expected: Both the UI and Content font changes to OpenDyslexic
4)Click Input
5)Click Cancel
Observed and Expected: Both the UI and Content font reverts to SystemFont
as we cancelled our selection
6)Click cog
7)Click Display
8)Change font( say, from SystemFont to OpenDyslexic)
Observed and Expected: Both the UI and Content font changes to OpenDyslexic
9)Click Input
10) Now, I want to click ApplySettings. But this button is disabled here,
whereas the Cancel button is enabled(as we saw in the previous steps). If
the Cancel button is enabled, why should the ApplySettings button be
disabled even though the selection is changed by the user.

I would like to contribute by writing feature files but want to learn
cucumber a bit and then begin..
Meanwhile, if I notice a observation/bug in ULS, is it okay if I enter it
in bugzilla after checking that its not a duplicate?

Thanks,
Renuka

On Sat, Aug 31, 2013 at 8:52 PM, <qa-request at lists.wikimedia.org> wrote:

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