451
edits
QA/Jetpack/AddonBuilderTestPlan: Difference between revisions
Jump to navigation
Jump to search
QA/Jetpack/AddonBuilderTestPlan (view source)
Revision as of 21:02, 30 September 2010
, 30 September 2010→QA Reports
| Line 20: | Line 20: | ||
** Chrome 4+ | ** Chrome 4+ | ||
<br> | <br> | ||
There will be two types of testing for Add-on builder. | There will be two types of testing for Add-on builder.<br> | ||
1. Manual | 1. Manual | ||
2. Automation | 2. Automation | ||
1. Manual: | '''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. | |||
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.<br> | |||
'''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. | 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 - | The flow can be - | ||