B2G/QA/Test Plan Review: Difference between revisions
No edit summary |
|||
| Line 20: | Line 20: | ||
== External Workflow == | == External Workflow == | ||
Externally, you should aim to gather feedback from reviewers from the following roles on your feature: | |||
* Developer Lead | |||
* UX Lead | |||
* Product Lead | |||
Revision as of 15:44, 16 April 2013
Overview
The following document summarizes the process for executing an effective test plan review for B2G features.
Internal QA Workflow
Internally, you should aim to have at least one reviewer review your test plan analyzing two main themes:
- Quality of the test coverage itself
- Understandability of test coverage
Quality of the test coverage itself analyzes if the test cases for the feature sufficiently cover happy path and negative cases sufficiently for each user story. Understandability of the test coverage analyzes if the test cases for the feature can be understood by a person who did not create the test cases to allow that same person to run that test case without ambiguity.
To setup a review for a test plan, you should generate a query off of MozTrap that contains the relevant test cases for the feature and provide that to the reviewer. Then, the reviewer can send his review results in the following form:
- Quality of test coverage - review+ for pass, review- for needs work
- Understandability of test coverage - review+ for pass, review- for needs work
- Additional comments explaining rationale behind review decisions
External Workflow
Externally, you should aim to gather feedback from reviewers from the following roles on your feature:
- Developer Lead
- UX Lead
- Product Lead