Confirmed users
3,727
edits
QA/BrowserID/TestPlan: Difference between revisions
→Strategy
| Line 3: | Line 3: | ||
= Strategy = | = Strategy = | ||
Create a consistent and repeatable set of tests for qualifying and releasing the weekly builds and deployments for BrowserID. The focus needs to be on quality, but also on providing accurate feedback on successes and issues to Dev and PM so that Production releases provide a useful product for the Mozilla and development communities. | |||
Ad Hoc testing to define test paths on the client and server side. | |||
Create useful client-side and server-side test cases that can be imported into Litmus for repeatable manual testing. | |||
Create automated client and server tests that can more accurately cover the full functionality of the UI, the API, and the main roles (PIA, RP, IP) and various flows. | |||
Emphasis on security and privacy issues that might come up across OS, browsers, accounts, and emails on the various clients tested against the server. | |||
Identifying and tracking issues in GitHub and Bugzilla. | |||
Provide useful metrics to Dev and PM. | |||
= Scope of Testing = | = Scope of Testing = | ||