Quality Assurance

From MediaWiki.org
(Redirected from QA and testing)
Jump to: navigation, search

We help to test and help to evaluate the quality of Wikimedia software projects. Our processes and activities are open to the whole 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.

Because our QA effort is spread across Wikimedia Engineering we are not always 100% engaged with every project. We have a guide on when to use QA services.

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

Contents

Status[edit]

2013-06-03:

QA is bringing ULS tests online. We made a test spike for VisualEditor and will expand that with our new OPW intern. Still working to turn builds from red to green: tweaking tests, shepherding bugzilla tickets for test environments, etc.


See also the QA Strategy and Roadmap.

Features testing[edit]

Hammer - Noun project 1306.svg

QA on new features is assessed mainly through manual testing of the 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.

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

For more details, see Features testing.

We practice three levels or approaches to Features testing.

Browser testing[edit]

Noun project 8974.svg

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

We are looking for contributors! Technical experience is NOT required.

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

For more details, see Browser testing.

See also[edit]