B2G/QA/Test Plan Review: Difference between revisions

Jump to navigation Jump to search
Line 32: Line 32:
To setup a review for a test plan with external parties, you should generate a high-level list of the test cases with titles only in an etherpad or shared document that external parties can interact with. Then, the external parties can send his review results in the following form on a per role basis:
To setup a review for a test plan with external parties, you should generate a high-level list of the test cases with titles only in an etherpad or shared document that external parties can interact with. Then, the external parties can send his review results in the following form on a per role basis:


* Development Code Review by Developer Lead - review+ for sufficient coverage, review- for coverage needing improvement
* Development Code Flow Coverage by Developer Lead - review+ for sufficient coverage, review- for coverage needing improvement
* UX Flow Review by UX Lead - review+ for sufficient coverage, review- for coverage needing improvement
* UX Flow Coverage by UX Lead - review+ for sufficient coverage, review- for coverage needing improvement
* Product Review by Product Lead - review+ for sufficient coverage, review- for coverage needing improvement
* Requirements Coverage by Product Lead - review+ for sufficient coverage, review- for coverage needing improvement
* Additional comments explaining rationale behind review decisions
* Additional comments explaining rationale behind review decisions
Confirmed users
2,959

edits

Navigation menu