451
edits
QA/Jetpack/AddonBuilderTestPlan: Difference between revisions
Jump to navigation
Jump to search
QA/Jetpack/AddonBuilderTestPlan (view source)
Revision as of 19:50, 30 September 2010
, 30 September 2010no edit summary
(Created page with "== Introduction == '''Mozilla Add-on builder''' Mozilla Add-on Builder is the quick and easy way to develop an extension for Firefox using common web technologies. It is the GUI...") |
No edit summary |
||
| Line 1: | Line 1: | ||
== Introduction == | == 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 [https://builder.mozillalabs.com/ here]. | |||
=='''Criteria to ship'''== | |||
<br> | |||
Add-on builder can be pushed to production when the tests pass. In these tests, we should basically be 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. | |||
=='''QA Reports'''== | |||
<br> | |||
There will be two types of testing for Add-on builder. | |||
1. Manual | |||
2. Automation | |||
1. Manual: | |||
Manual testing includes running Smoke tests, BFTs and FFTs manually. 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. | |||
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 | |||
- 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. | |||
== Add-on builder == | |||
{| class="standard-table" style="width: 100%;" | |||
|- | |||
| class="header" | Milestone | |||
| class="header" | Release Date | |||
| class="header" | QA Sign off | |||
| class="header" | Status | |||
|- | |||
| [https://wiki.mozilla.org/Labs/Jetpack/SDK/0.8#Timeline SDK 0.8] | |||
| September 22 | |||
| | |||
| '''Mac''':result<br> '''Windows''':result<br> '''Linux''':result<br> | |||
|- | |||
| [https://wiki.mozilla.org/Labs/Jetpack/SDK/0.7#Timeline SDk 0.7] | |||
| August 26 | |||
| | |||
| '''Mac''':result<br> '''Windows''':result<br> '''Linux''':result<br> | |||
|} | |||