451
edits
QA/Jetpack/AddonBuilderTestPlan: Difference between revisions
Jump to navigation
Jump to search
→QA Strategy
| Line 28: | Line 28: | ||
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> | 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> | ||
Following is the list of the features that are implemented in the Add-on builder. | |||
Here are the use cases: | |||
'''2. Automation:''' | '''2. Automation:''' | ||
| Line 46: | Line 50: | ||
This is a sample example for automation flow. We will have scripts to test different features like badging verification, notification verification etc. | 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 == | == Schedule == | ||