Confirmed users
9,511
edits
QA/Jetpack/AddonBuilderTestPlan: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 31: | Line 31: | ||
There are two types of testing for Add-on builder.<br> | There are two types of testing for Add-on builder.<br> | ||
''' | '''=== Manual: ===''' | ||
Manual testing includes running Smoke tests, BFTs and FFTs. They should pass in order to release Add-on builder. We will use spot checks for feature testing to ensure that when new features land, they do not regress any functionality in the application and behave as expected.<br> | Manual testing includes running Smoke tests, BFTs and FFTs. They should pass in order to release Add-on builder. We will use spot checks for feature testing to ensure that when new features land, they do not regress any functionality in the application and behave as expected.<br> | ||
| Line 39: | Line 39: | ||
* [https://wiki.mozilla.org/QA/Jetpack/AddonBuilderTestPlan/Testcases Test cases] | * [https://wiki.mozilla.org/QA/Jetpack/AddonBuilderTestPlan/Testcases Test cases] | ||
''' | '''=== Automation ===''' | ||
GitHub repository for tests: https://github.com/ayanshah/FlightDeck-selenium/ | |||
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. | ||