B2G/QA/WebAPI Test Plan/Instructions for Contributors: Difference between revisions

B2G/QA/WebAPI Test Plan/Instructions for Contributors (view source)

9 bytes added , 21 July 2012

canmove, Confirmed users

2,041

edits

@@ Line 10: / Line 10: @@
 We have two goals. One is acceptance testing of the APIs as implemented in Firefox OS. The other is implementing regression tests that will run from here on out to aid new development.
-Acceptance testing is the more important goal in the short term for QA. I emphasize this because for development's short-term purposes, there is more focus on regression testing. However, QA has to sign off on the final version on a device so we have an acceptance requirement as well. Regression testing is still important, but we need acceptance tests in place prior to Firefox OS shipping.
+Acceptance testing is the more important goal in the short term for QA, as it's driven by the date of the final release. This must be balanced against development's primary goal, getting more regression tests in place. The regression tests are important, and should be a portion of every API's test plan. However, a strategy that gives us regression tests but no acceptance tests will make signoff risky.
 ==How==
@@ Line 38: / Line 38: @@
 ==Procedure==
-I fully expect you to have a ton of questions while you do this. Please don't hesitate to ask Geo Mealer via [mailto:gmealer@mozilla.com my email] or on IRC (user:geo).
+I fully expect you to have a ton of questions while you do this. Please don't hesitate to ask Geo Mealer via [mailto:gmealer@mozilla.com email] or on IRC (user:geo).
 # Pick a Ready area from the [[B2G/QA/WebAPI_Test_Plan|Test Plan]]<br/><br/>