Quality Assurance

Quality Assurance and testing efforts are organized in two major areas: manual testing of new features and automated browser testing. You can use the documentation and processes described below for your own projects. Check our QA/Roadmap

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

Status
See also our roadmap.

Features testing
QA on new features is assessed mainly through manual testing of software build through the continuous integration process. Developers and community testers manually check function and features, either on their own or through organized testing activities.

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 - see How to report a bug.
 * Collaborating with others to specify proper behavior of software features to be checked.

Some Wikimedia teams have specific testing guidelines and documentation:


 * Echo notifications testing
 * Mobile QA
 * Visual Editor (in Wikipedia)
 * See also the list of Wikimedia Features projects

If you are interested in manual/feature/functional testing, join the proposed MediaWiki Group Feature testing.

Browser testing
We also create and maintain automated browser-level tests with a focus on compatibility and regressions.

For more details, see Browser testing.

Contributing to Browser testing may take several forms


 * Contributing directly to the automation. Technical experience is NOT required. Currently this is our foremost need.
 * 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.

If you are interested in automated browser tests, join the proposed MediaWiki Group Browser testing.

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


 * Test backlog: prioritized list of tests to be automated


 * 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

 * Beta cluster
 * 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