QA/Jetpack/AddonBuilderTestPlan: Difference between revisions

QA/Jetpack/AddonBuilderTestPlan (view source)

162 bytes added , 1 October 2010

no edit summary

451

edits

@@ Line 5: / Line 5: @@
 =='''Criteria to ship'''==
-Add-on builder can be pushed to production when the tests pass. In these tests, we should basically be able to write the code for the add-on inside the bespin editor and download it to Firefox to check if it works. There will be sample Add-on and library code to test with. You can use this code in order to check whether the libraries and add-ons are generated.
+Add-on builder can be pushed to production when the manual as well as automation tests pass. In these tests, we should make sure that:
+** Smoketests, BFTs and FFTs should pass.
+** We are able to write the code for the add-on inside the bespin editor and download it to Firefox to check if it works.
+<br>
+There will be sample Add-on and library code to test with. You can use this code in order to check whether the libraries and add-ons are generated. See the QA strategy section below for details on how and what to test.
 =='''QA Strategy'''==