451
edits
QA/Jetpack/AddonBuilderTestPlan: Difference between revisions
Jump to navigation
Jump to search
→Criteria to ship
No edit summary |
|||
| Line 6: | Line 6: | ||
=='''Criteria to ship'''== | =='''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: | 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> | <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. | 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'''== | =='''QA Strategy'''== | ||