QA/Jetpack/AddonBuilderTestPlan: Difference between revisions
m (→QA Strategy) |
|||
| Line 9: | Line 9: | ||
* The add-ons and libraries are being saved. | * 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 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. 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. | ||
Revision as of 20:44, 1 October 2010
Introduction
Add-on builder
Add-on Builder is the quick and easy way to develop an extension for Firefox using common web technologies. It is the GUI version of the Jetpack SDK. If you do not have an extensive experience of programming using text editors and revision control systems, use the Add-on builder for the awesome experience of creating add-ons for Firefox. Get started by clicking here.
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:
- 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.
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.
| Browsers | Platforms |
| Firefox 3.6+ | Mac OS X 10.6 and higher Windows XP, Vista and 7 Linux |
There are two types of testing for Add-on builder.
1. Manual:
Manual testing includes running Smoke tests, BFTs and FFTs. They should pass in order to release Add-on builder. We can use spot checking for feature testing, just to make sure that landing a feature does not break the overall functionality.
Following is the list of the features that are implemented in the Add-on builder and its use cases.
2. Automation:
Being a web application, Add-on builder is a great candidate for automation tests. Here, we can basically test the flow of creating an add-on through Add-on builder. We can also test the creation of libraries as well. The flow can be -
- Login - Click on create Add-on - Typing in text editor for module - (Optional)Save - (Optional)Add attachment(s) - (Optional)save - (Optional)Add libraries - Edit add-on information - Save - Download add-on - Install to browser
This is a sample example for automation flow. We will have scripts to test different features like badging verification, notification verification etc. (Talk about the tool to be used here)
Schedule
| Milestone | Release Date | QA Sign off | Browser Status | Platform Status |
| 1.0a5 | September 22 | Firefox:result | Mac:result Windows:result Linux:result |