[QA] help update the QA wiki pages? (new people welcome!)

[Željko Filipin]

On Fri, Nov 15, 2013 at 3:14 AM, S Page <spage at wikimedia.org> wrote:

> "Running and writing browser tests" is a small maze of outdated
> instructions, a transcluded page, a redirect, and some confusion over
> running tests locally vs. running MediaWiki locally and/or in vagrant.
>
> I think one order of diving in to browser tests is:
>
> * go look at test results on cloudbees
> * investigate a test that's failing
> * view the code for that test
> * if you manually go through the test's steps on a wiki site and it fails
> for you, then file a bug
>
> (This doesn't require any local code at all, it's all on the web.) Next
> level:
>
> * get the test code on your machine
> * run cucumber locally, pointing to some MediaWiki install
> * see if the code fails for you
> * if it does, try fixing the test, and rerun cucumber
>
> * if you find an error in a test, either update a bug
> * or better yet contribute it in gerrit
>
> None of these steps require you to have a working local MediaWiki. The
> recent edit (from Jeff Hall ? Hi!) suggests enabling the visualeditor role
> in MediaWiki-Vagrant to run the VE tests, which works but may be overkill.
>
> Hope this helps. "There's more than one way to do it."
>

S,

it would be great if you would document this at mediawiki.org.

Željko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/qa/attachments/20131120/d72806bc/attachment.html>