QA/Jetpack/AddonBuilderTestPlan: Difference between revisions
Dandonkulous (talk | contribs) |
Dandonkulous (talk | contribs) |
||
| Line 10: | Line 10: | ||
== Criteria to ship == | == Criteria to ship == | ||
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. | * All links on the website are working. There should be no 404 errors. | ||
* The add-ons and libraries are being saved. | * The add-ons and libraries are being saved. | ||
* We are able to write the code for | * 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. | ||
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 == | == QA Strategy == | ||
Revision as of 23:31, 5 October 2010
Introduction
The Add-on Builder is the quick and easy way to develop an extension for Firefox using common web technologies. The Builder is essentially a web app that wraps the Add-on SDK for developers who do not possess extensive experience developing add-ons for Firefox or are not familiar with console-based development environments. Get started by clicking here.
Release Planning and Implementation
The linked document below is used for planning and development of specs for upcoming releases of the Add-ons Builder. See the features link in QA strategy section for the list of major features that have been implemented to date.
Add-on Builder Product Development Plan
Criteria to ship
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 an add-on inside the Skywriter editor and download it to Firefox to ensure it works as expected.
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
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 test 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.
- Tools used
- WIP(Talk about the automation 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 |