Confirmed users
2,959
edits
B2G/QA/Test Plan Review: Difference between revisions
Jump to navigation
Jump to search
→External Workflow
| Line 36: | Line 36: | ||
To setup a review for test cases 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 test cases 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 Flow Coverage 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 | ||
| Line 42: | Line 41: | ||
* Requirements Coverage 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 | ||
'''Note: ''' One reviewer per each role (development, UX, product) is the minimum requirement, but that should not stop you from getting more reviewers to look at your test cases if think there's value to having more reviewers. | '''Note: ''' One reviewer per each role (development, UX, product) is the minimum requirement, but that should not stop you from getting more reviewers to look at your test cases if think there's value to having more reviewers. | ||