451
edits
QA/Jetpack/AddonBuilderTestPlan: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 10: | Line 10: | ||
[https://docs.google.com/document/edit?id=1q680sqwBaJ-0uz25tbi_osLJfi4UIBnBFtWAUVOHg2E&hl=en# Add-on Builder Product Development Plan] | [https://docs.google.com/document/edit?id=1q680sqwBaJ-0uz25tbi_osLJfi4UIBnBFtWAUVOHg2E&hl=en# Add-on Builder Product Development Plan] | ||
== | == 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: | ||
* All links on the website are working. There should be no 404 errors. | * All links on the website are working. There should be no 404 errors. | ||
| Line 17: | Line 17: | ||
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 == | ||
The Add-on builder will be tested on different platforms and environments. | The Add-on builder will be tested on different platforms and environments. | ||