Quality Assurance

Documents
The QA/testing effort is divided roughly into two or possibly three areas.

One is "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:


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

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:


 * We would like to make this Group a central repository for knowledge and practice of automated browser testing

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


 * Our QA strategy, especially around engaging volunteers


 * QA/Roadmap


 * Testing portal (historical, out of date in places)
 * The first week of training QA staff get
 * /Specifications/
 * Status updates
 * Browser test automation discussion

Related

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