Quality Assurance

We help testing and evaluating the quality of the Wikimedia software projects. Our processes and activities are open to all the MediaWiki community. Contributors of any background and experience are welcome. From engaged users to QA professionals: we have a task for you. All you need is curiosity for unexplored areas and attention to detail.

Quality Assurance and testing efforts are organized in two major areas: manual testing of new features and automated browser testing.

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

Status
See also our Strategy and 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.

Beta cluster is offered to teams deploying new features to Wikimedia projects. If you want to test bleeding edge versions of Wikipedia check http://test.wikipedia.org & http://test2.wikipedia.org

MediaWiki developers can use Wikimedia Labs to have their own testing environment. See also the MediaWiki Manual pages for Unit testing.

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.