QA/Jetpack/AddonBuilderTestPlan/Testcases: Difference between revisions

← Older edit

QA/Jetpack/AddonBuilderTestPlan/Testcases (view source)

Revision as of 20:38, 28 April 2011

100 bytes added , 28 April 2011

→‎Add-on Editor Page

Ashah

451

edits

@@ Line 32: / Line 32: @@
 **When in View mode, the library editor should have "Copy", "Revision", "Properties" buttons.<br>
 **Clicking on Copy button should create a fresh new package with the copied contents from the original package.
-**<font color="Red">The user should be able to add/remove Lib(modules) and Libraries and the list of modules/libraries should be updated.</font>
-**<font color="Red">The revision should change when the user adds/removes libs(modules)/data(attachments) and libraries.</font>
 **The "Revision" button should display all the revisions that have been recorded for that add-on.
 **The information of the current add-on can be edited by clicking the "Properties" button on the editor. (Note:You should be in the edit mode for this to work.)
@@ Line 39: / Line 37: @@
 **A new revision should be generated when the user saves after making changes to the existing addon code.
 **The code for the add-on library should be saved when the save button is pressed.<br>
+**<font color="Red">The user should be able to add/remove Lib(modules) and Libraries and the list of modules/libraries should be updated.</font>
+**<font color="Red">The revision should change when the user adds/removes libs(modules)/data(attachments) and libraries.</font>
 **<font color="Red">The SDK version to be used for the current add-on can be changed from the plugins(libraries) section.</font>
 **<font color="Red">When the user hits download without saving the code, the downloaded XPI should still contain the final edits of the user(i.e.it should check for a edit after the last save, and if true, should autosave it in the XPI)</font>
@@ Line 46: / Line 46: @@
 **<font color="Red">The revision should also be updated when you edit the name of the attachment.</font>
 **<font color="Red">You should be able to add a file successfully.</font>
-**<font color="Red">You should be able to upload an attachment using an external URL.<font>
+**<font color="Red">You should be able to upload an attachment using an external URL.</font>
 **<font color="Red">If a library is added to an addon and if it is updated in another tab, you should be able to see a refresh icon on mouse over the library is the addon editor.</font>
+**<font color="Red">Check that Edit and save of the version and comment are working in the save button</font>
 *Manual(in-litmus):
@@ Line 55: / Line 56: @@
 **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 ('Data' button on the page).
+**The user should be able to upload attachments ('Data' button on the page).
+**The user should be able to add attachments from an URI (2 MB max filesize).
 **Adding attachments should update the revision number of the current addon.
 **If the user is in the "Edit" mode, the attachments should be editable in the text editor. The editable attachments are .js, .css and .txt)
@@ Line 64: / Line 66: @@
 **The add-ons/libraries on this page should be tagged "initial"(default) for newly saved packages.
 **It should be tagged "copy" for copied new packages.
-**<b>It should be tagged "uploaded" for packages that have been uploaded.</b>
+**The page should also show the count of the number of add-ons and libraries  that you have created.<br>
-**The page should also show the count of the number of add-ons and libraries  that you have created.(done)<font color="Red"></font> <br>
 **When clicking on the "Public Add-ons"/"Public Libraries" link, add-ons/libraries should be shown in a pagination manner if there are more than 10 add-ons for the user.
 **When clicking on the "Private Add-ons"/"Private Libraries" link, add-ons/libraries should be shown in a pagination manner if there are more than 10 add-ons for the user.
@@ Line 71: / Line 72: @@
 **On the dashboard, each library must have "Edit", "Delete", "Public" and "Private" buttons.
 **Clicking on Private button disables the add-on/library and sends it to Private add-ons/Private libraries section.
-**<b>You can reactivate the private add-on by clicking the "Public" button from the Private add-ons page.</b>
+**You can reactivate the private add-on by clicking the "Public" button from the Private add-ons page.
-**<b>You can reactivate the private libraries by clicking the "Public" button from the private libraries page.</b>
+**You can reactivate the private libraries by clicking the "Public" button from the private libraries page.
-**<b>Clicking on the "Private add-ons" link should show you the currently disabled addons.</b>
+**Clicking on the "Private add-ons" link should show you the currently disabled addons.
-**<b>Clicking on the "Private libraries" link should show you the currently disabled libraries.</b>
+**Clicking on the "Private libraries" link should show you the currently disabled libraries.
-**You can upload an xpi file from your computer by clicking the "upload package" link on this page.
 ** You should be able to go to editor page when you click edit button.
-** Add on should be installed when you hit the Test button.
 ** Add on should be permanently deleted when you hit the Delete button
 *Manual (in-litmus)
-**<font color="Red">All the saved and public (default) Addons and libraries should be shown on this page.</font>
+**All the saved and public (default) Addons and libraries should be shown on this page.
+**It should be tagged "uploaded" for packages that have been uploaded.
+**You can upload an xpi file from your computer by clicking the "upload package" link on this page.
+** Add on should be installed when you hit the Test button.
 ==Library editor page==