Quality Assurance

Testing strategies
The QA/testing effort is divided into two major areas:

Features testing
This is our manual checking of function and features, done by staff, by developers, and by 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. People interested in this aspect of QA/testing are encouraged to join our new Group:


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

Browser testing
The other main thrust for QA/testing is creating and maintaining automated browser-level tests. People interested in automated browser tests are encouraged to 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.

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


 * QA/Roadmap


 * QA/test backlog prioritized list of tests to be automated


 * QA/Browser testing/community automated browser testing more theoretical discussion of browser testing approach


 * QA/running and writing 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


 * Testing portal (historical, out of date in places)
 * /Specifications/ (not sure this belongs here, or even if it is still true)
 * Status updates (made obsolete by this page)
 * Browser test automation discussion (historical, mostly made obsolete by actual projects)

Related

 * Browser testing
 * Browser test automation discussion (historical, possibly out of date)
 * Beta cluster
 * Mobile QA
 * Continuous integration
 * Bugzilla