Quality Assurance/Roadmap

Our mission is to help improve the quality of WMF software, working both within WMF itself and with the greater Wikipedia community and with the greater software testing community.

This page describes our current projects in regard to that mission.

=Projects=


 * Browser test automation
 * Features testing with the community
 * Process work and continuous improvement (secondary for Q1/Q2 2013)

Activities

 * Creating browser tests/increasing test coverage (including Mobile) [CHRIS, ZELJKO, MICHELLE] [ONGOING]
 * QA/test backlog
 * Also see http://wikitech.wikimedia.org/view/Eqiad_Migration_Planning/Checklist for automation suggestions, Chris is currently implementing delete/restore tests for files
 * Features testing with the community [CHRIS, QUIM] [ONGOING]

How we prioritize our work

Browser test automation

 * Jenkins [ZELJKO, CHRIS] [ONGOING]
 * Cloudbees https://wmf.ci.cloudbees.com/
 * Selenium/Watir https://gerrit.wikimedia.org/r/#/admin/projects/qa/browsertests https://github.com/wikimedia/qa-browsertests [ZELJKO, CHRIS] [ONGOING]
 * Sauce Labs https://saucelabs.com/account (with Cloudbees account)
 * test2wiki http://test2.wikipedia.org/ [WMF, CHRIS]
 * beta labs http://en.wikipedia.beta.wmflabs.org/ [ANTOINE, CHRIS, RYAN LANE]
 * gerrit and git
 * Documentation and architecture [CHRIS, EVERYONE] [ONGOING]
 * How to contribute to browser testing
 * Running and writing browser tests
 * Acceptance Test Driven Development/Page Objects/Test Steps (noted in docs above, subject to rewrite) [CHRIS, QUIM, EVERYONE]

Features testing

 * Iterative deployment (historical) QA/WTA_Test_Plan
 * AFT (historical) QA/Article_Feedback_Test_Plan
 * Echo(?) upcoming Echo/Testing

Community

 * Features testing group
 * Browser testing group