QA/Jetpack/AddonBuilderTestPlan: Difference between revisions

QA/Jetpack/AddonBuilderTestPlan (view source)

143 bytes added , 5 October 2010

1,273

edits

@@ Line 10: / Line 10: @@
 == Criteria to ship ==
-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:
+The Builder can be pushed to production when the manual and automated tests pass based on the following criteria:
 * All links on the website are working. There should be no 404 errors.
 * The add-ons and libraries are being saved.
-* 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.
+* We are able to write the code for an add-on inside the Skywriter editor and download it to Firefox to ensure it works as expected.
-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.
+A test Add-on and Library will each be created that possess all the possible attributes of a fully featured package. Each item included in the Add-on or Library will be entered into the Builder and tested in a stepwise process that mocks the route a developer would take in creating such a package. See the QA strategy section below for details on how and what to test.
 == QA Strategy ==