Quality Assurance/Roadmap
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
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
edit- Browser test automation
- Features testing with the community
- Process work and continuous improvement (secondary for Q1/Q2 2013)
Activities
edit- 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
- Features testing with the community [CHRIS, QUIM] [ONGOING]
Infrastructure
editBrowser test automation
edit- Jenkins [ZELJKO, CHRIS] [ONGOING]
- Cloudbees https://wmf.ci.cloudbees.com/
- Selenium/Watirhttps://de.wikimedia.org#e/adminhttps://github.com/wikimedia/qa-search [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
edit- Iterative deployment (historical) QA/WTA_Test_Plan
- AFT (historical) QA/Article_Feedback_Test_Plan
- Echo(?) upcoming Echo/Testing