Selenium/Ruby/Browser testing

Rationale
It's tedious to manually test Wikimedia sites within the thousands of browser/operating system combinations that are out there, so we do automated testing to find errors and assure quality.

We use Cucumber because it lets you write tests in plain English; you don't need to know Ruby.

Timeline

 * October to now: Mobile QA Engineer Michelle Grover is creating an automatable regression test suite for MobileFrontend. These tests are currently running as builds under a hosted instance of Jenkins, with the intention of moving them to the WMF Continuous Integration environment pending upgrades to the machines hosting Gerrit and Jenkins.
 * Late October, early November: ported existing tests from RSpec to Cucumber, focusing on UploadWizard
 * November: Chris McMahon to introduce Cucumber to feature development soon. He aims to socialize Cucumber acceptance test-writing (using "given-when-then" format) in browser testing, to get developers to more regularly write these tests as they work and commit. He'll be talking to Fabrice, Arthur, Siebrand, James Forrester, and probably Tomasz. Coverage goals: extensions that are on beta or test2 right now.

Resources

 * Code: see Filipin's code in GitHub and then the qa/browsertests repository in Gerrit.
 * Test plan: see the backlog of tests to be automated
 * User requirements:
 * Specifications: Browser test automation discussion
 * Software design document:
 * Documentation plan:
 * User interface design docs:
 * Schedule:
 * Task management:
 * Release management plan:
 * Communications plan:

We use "given-when-then" testing format.

Communications

 * Past status messages