Quality Assurance

We organize Quality Assurance and testing in two major areas: manual testing of new features and automated browser testing.

We also collaborate with Bug management, Continuous integration and other Wikimedia Engineering teams.

Features testing
We manually check function and features ("we" meaning staff, developers, and the greater community). Sometimes this testing is done as an asynchronous project, sometimes it is done as a synchronous real-time exercise, and sometimes it is ad hoc. If you're interested in this aspect of QA/testing, join our new Group:


 * Feature testing group page - We would like to center our manual/feature/functional testing in a Group of interested people.

Contributing to Features testing may take several forms:


 * Helping organize test efforts or test events
 * Checking software under development for proper function
 * Reporting issues in Bugzilla
 * Collaborating with others to specify proper behavior of software features to be checked

Browser testing
We also create and maintain automated browser-level tests. If you're interested in automated browser tests, join our other new Group:


 * Browser testing group page - We would like to make this Group a central repository for knowledge and practice of automated browser testing.

Contributing to Browser testing may take several forms


 * Contributing directly to the automation Technical experience is NOT required.  This is our foremost need in early 2012.
 * Running automated browser tests locally
 * Analyzing test results and reporting failures discovered by way of Jenkins
 * Contributing code for tests to be executed in browsers using Cucumber and the page-object gem. gerrit github. Also see Contributing directly to the automation above

Other important documents
This is how we are engaging the QA/testing community:


 * QA/Roadmap


 * Test backlog: prioritized list of tests to be automated


 * Community automated browser testing: more theoretical discussion of browser testing approach


 * How to write and run browser tests: more technical discussion of browser automation framework


 * Our QA strategy, especially around engaging volunteers

Browser test source code
 * https://gerrit.wikimedia.org/r/#/admin/projects/qa/browsertests
 * mirror: https://github.com/wikimedia/qa-browsertests

Current browser test results (hosted on Cloudbees with access to Sauce Labs test runs)
 * https://wmf.ci.cloudbees.com/

Training overview
 * The first week of training QA staff get


 * /Specifications/ (not sure this belongs here, or even if it is still true)
 * Past status updates

Related

 * Browser testing
 * Browser test automation discussion (historical, possibly out of date as new projects arise)
 * Beta cluster
 * Mobile QA
 * Bugzilla & How to report a bug
 * Test wiki: http://test2.wikipedia.org
 * Mobile browser testing
 * Database testing
 * Manual:Unit testing
 * Manual:PHP unit testing
 * Manual:JavaScript unit testing
 * Fixing broken tests
 * Category:MediaWiki_test_plans