QA/Jetpack/AddonBuilderTestPlan/Testcases
< QA | Jetpack | AddonBuilderTestPlan
Jump to navigation
Jump to search
LEGEND:
Black = Done
Red = Pending
Blue = Blocker
Following are the test cases for the Add-on builder.
- Home Page:
- Automated:
- User should be able to login to add-on builder through the Sign-in button on the home page. The Dashboard should be displayed.(done)
- User should be redirected to the text editor page when clicked on the create add-on button, after he is authenticated.(done)
- All links on the home page should be clickable and redirected to the proper page.
- When the user is not logged in,the home page should only show the "Test" and "View Source" buttons(enabled).(done)
- Apart form the above mentioned buttons, "Edit" and "Disable" buttons should be shown on the home page to the user for the add-ons that have been created by them.(user needs to be logged in)(done)
- User should be redirected to the library text editor page when they click on "Create Library" button (done)
- Automated:
- Manual(in-litmus):
- Latest Jetpack SDK should be downloaded when the user clicks on the "Download Add-ons builder SDK"
- Manual(in-litmus):
- Editor Page:
- This page has two phases for Add-ons and Libraries:
- View
- Edit
- Automated:
- When in Edit mode, the add-on editor should have four buttons: "Test", "Download", "Save", "Revision".(done)
- When in View mode, the add-on editor should have four buttons: "Test", "Download", "Copy", "Revision".(done)
- When in Edit mode, the library editor should have "Save" and "Revision" buttons.(done)
- When in View mode, the library editor should have "Copy" and "Revision" buttons.(done)
- Clicking on Copy button should create a fresh new package with the copied contents from the original package.(done)
- The revision should change when the user adds/removes modules (done)The total number of modules added should be displayed in the modules section (done)
- The "Revision" button should display all the revisions that have been recorded for that add-on.(done)
- The information of the current add-on can be edited by clicking on the add-on name. (Note:You should be in the edit mode for this to work.)
- You should *NOT* be able to change the information of the add-on in view source mode.(done)
- The user should be able to add modules and libraries
- A new revision should be generated when the user saves after making changes to the existing addon code.(done)
- The code for the add-on library should be saved when the save button is pressed.(done)
- The SDK version to be used for the current add-on can be changed from the libraries section.
- The revision should change when the user adds/removes libraries
- The total number of libraries added should be displayed in the libraries section
- This page has two phases for Add-ons and Libraries:
- Manual(in-litmus):
- The "Test" button should install the add-on into the browser without a restart. It should change state to "pressed" after the addon is installed
- Clicking on the pressed button again will uninstall the addon and the button will be released.
- Clicking on the "Download" button should generate an XPI file.
- The user should be able to add attachments.
- Adding attachments should update the revision number of the current addon.
- Manual(in-litmus):
- My account page:
- Automated:
- The add-ons on this page should be tagged "initial"(default) for a newly saved packages.(done)
- It should be tagged "copy" for copied new packages.(done)
- The page should also show the count of the number of add-ons that you have created.(done)
- When clicking on the "Your Add-ons"/"Your Libraries" link, add-ons/libraries should be shown in a pagination manner if there are more than 10 add-ons for the user.(done)
- In "Your Latest Add-ons" section, each add-on must have "Test", "View Source", "Edit" and "Disable" buttons.(done)
- In "Your Latest Libraries" section, each library should have "View Source", "Edit" and "Disable" buttons.(done)
- This page should show you the total count of the number of add-ons and the number of libraries that you have created.(done)
- Clicking on disable button disables the addon
- You can reactivate the disabled addon form the Disabled addons page.
- [Bug 579156] Add [Edit] button to view source mode navigation if user is the author of the package
- Automated:
- Manual (in-litmus)
- The saved and enabled (default) Addons and libraries should be shown on this page.
- Manual (in-litmus)
- Library editor page:
- Automated:
- The library should be saved through the "Save" button. (done in home page)
- The code for the library should be edited and should be saved when the save button is pressed.(done)
- Modules and libraries should be allowed to be added to the current library.
- Library information should be editable when clicked on the library name on that page(Note: This can be done only when the user is in edit mode)
- The revision can be checked through the revision button. (done,combined with above test case)
- The libraries created by the user should be reflected in the libraries section when the user is writing the code for an add-on.
- The library should be saved through the "Save" button. (done in home page)
- Automated:
- Manual:
- Attachments should be allowed to be added to the current library.
- Manual: