Last modified: 2014-01-08 14:37:16 UTC
Google Code-in home page: http://www.google-melange.com/gci/homepage/google/gci2013 Wikimedia Google Code-in landing page: https://www.mediawiki.org/wiki/Google_Code-In Wikimedia Google Code-in tasks: http://www.google-melange.com/gci/org/google/gci2013/wikimedia
Google Code-in QA tasks in Bugzilla: https://bugzilla.wikimedia.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=gci2013&sharer_id=16205
The goal is to have 5 tasks in status "open" at Google Code-in site at all times, in different categories if possible (coding, documentation...) so students have enough tasks to choose from. The bugs in Bugzilla should have enough information for a student to decide that the task is interesting enough to work on it.
From QA mailing list[1] As far as I remember, the guidelines for a good task are something that you would need 2-3 hours to finish = it would take 2-3 days for somebody new to the project. Having that in mind, this is a task that I plan to propose as a task: - find all QA related wiki pages at mediawiki.org and add QA category to them (then the mentor would either remove deprecated page from the category or mark them pages accordingly) - read a page (getting started, setup on a local machine, setup on Vagrant VM...), follow the advice and report/fix if something is outdated/wrong I have also noticed that we use both QA and Testing categories for most of the QA related pages. I do not mind which one we pick, but we should probably pick just one category. 1: http://lists.wikimedia.org/pipermail/qa/2013-November/000730.html
Task ideas: - Ruby files should use the new hash syntax[1] - Follow GitHub Ruby Styleguide[2]: "Prefer string interpolation instead of string concatenation" The above should be done for all our repositories that contain Ruby code[3] 1: http://www.ruby-doc.org/core-2.0.0/Hash.html 2: https://github.com/styleguide/ruby 3: https://github.com/wikimedia/mediawiki-selenium#links
If someone wants to make some selenium tasks for TimedMediaHandler, I think that'd be cool. (In particular, the whole embedplayer thing tends to break a lot with no one noticing. Has happened twice so far).
Could you please provide more information on what should be tested? I am looking for examples.
(In reply to comment #7) > Could you please provide more information on what should be tested? I am > looking for examples. I'm not exactly sure about the capabilities of selenium, but would something like the following be do-able: On the page https://commons.wikimedia.org/wiki/File:Paroxysm_at_Etna,_16-17_November_2013.webm?embedplayer=yes (or any video with the ?embedplayer=yes url argument. In normal use this url is embedded in another page, like wmf blog), click on the play button, make sure video actually starts playing
I am not sure that would be a good task for code-in, but we can try. :) Do you have more examples?
Task idea: replace @login Cucumber tag with warning in steps or page file.
