QA/Jetpack/AddonBuilderTestPlan/Usecases

From MozillaWiki
Jump to navigation Jump to search

Following are the use cases for the Add-on builder.

  • Home Page:
    • User should be able to login to add-on builder through the login button n the home page.
    • User should be redirected to the text editor page when clicked on the create add-on button, after he is logged in.
    • All links on the home page should be clickable and redirected to the proper page.
    • For add-ons that are shown on the home page, only the "Test" and "View Source" buttons should be enabled.
    • Apart form the above mentioned buttons, "Edit" and "Disable" buttons should be shown on the home page to the user for the addons that have been created by them.
    • Latest Jetpack SDK should be downloaded when the user clicks on the "Download Add-ons builder SDK"
    • User should be redirected to the library text editor page when they click on "Create Library" button
  • Editor Page:
    • The code for the add-on should be saved when the save button is pressed.
    • A new revision should be recorded for the current add-on when the "copy" button is clicked.
    • The "Revision" button should display all the revisions that have been recorded for that add-on.
    • The "Test" button should install the add-on into the browser without a restart.
    • Clicking on the "Download" button should generate an XPI file.
    • 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 cannot do this in view source mode)
    • The user should be able to add modules, libraries and attachments.
    • The SDK version to be used for the current add-on can be changed from the libraries section.
  • My account page:
    • The saved add-ons for the user should be shown on this page.
    • The add-ons on this page should be tagged whether they are "initial" or "copy".
    • The page should also show the count of the number of add-ons that you ahev created.
    • All the links present on this page should be working and should be redirected to their specific location.
    • The add-ons should be shown in a pagination manner if there are more than 10 add-ons for the user.
  • Library editor page:
    • Attachments, 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 library should be saved through the "Save" button. The revision should be generated through the revision button.
    • Te libraries created by the user should be reflected in the libraries section when the user is writing the code for an add-on.