Quality Assurance/When to use QA services
 | 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. |
Exploratory testing
[edit]Exploratory Testing is an embedded role within development teams at WMF. As your team lead for a QA person if you don't already have one!
If you need less specialized knowledge there is an on-demand third-party service that we use, please contact Greg Grossmeier for details.
Browser testing
[edit]Automated testing is writing and maintaining code that checks whether a feature performs as desired. These browser tests automatically look for regressions in multiple browsers using Selenium and report errors to Jenkins.
Some sorts of features are particularly amenable to browser testing:
- When the feature has user-facing/UI components
- When the feature is required to work in multiple browsers
- When a particular string is guaranteed as an outcome
Some times in the software development cycle are particularly amenable to browser testing:
- When the feature is considered more stable than unstable
- When regressions are a substantial worry
- When the development team does not anticipate making sweeping changes to string messages
- When the development team is in a position to make changes and improvements to the feature based on feedback from testing
- When the development team is in a position to learn how to write and maintain browser tests themselves