Firefox/HowTo-QA

Option #1

All completed Work (features, defects and changes) will be tested during and at the conclusion of each iteration.

Intra-Iteration Testing

• QA will test all completed Work (features, defects and changes) that has been landed and marked as 'Resolved'.
• Upon landing, QA will be 'flagged' to test the Work marked as 'Resolved'.
• Any new issues found will 'Reopen' the original Work subject to testing.
• The defect description/STR will be inserted as a comment in the Work subject to the testing.

Iteration End Testing

• QA will test all completed Work (features, defects and changes) marked as 'Resolved' from the current iteration only.
  • Variation: If resources permit, regression testing for all previously completed iterations can be conducted as well.
• Any new issues found will not 'Reopen' the original Work subject to testing but, instead, a new defect will be recorded.
• The new defect will be marked as a dependency to the Product Backlog and to the original Work subject to testing as a dependency.
• The new defect will be triaged at the Product Backlog Refinement Meeting for priority.

Option #2

A full regression test of all previously completed Work (features, defects and changes) will be conducted at the end of each iteration.

• QA will test all completed Work (features, defects and changes) marked as 'Resolved' from the current iteration.
  • Variation: If resources permit, regression testing for all previously completed iterations can be conducted as well.
• Any new issues found will not 'Reopen' the original Work subject to testing but, instead, a new defect will be recorded.
• The new defect will be marked as a dependency to the Product Backlog and to the original Work subject to testing as a dependency.
• The new defect will be triaged at the Product Backlog Refinement Meeting for priority.

Notes

• Any reliance upon QA is dependent upon QA agreeing to work in one of these ways.