451
edits
QA/Jetpack/AddonBuilderTestPlan/Testcases: Difference between revisions
QA/Jetpack/AddonBuilderTestPlan/Testcases (view source)
Revision as of 23:06, 13 April 2011
, 13 April 2011→Add-on Editor Page
| Line 27: | Line 27: | ||
**Edit | **Edit | ||
*Automated: | *Automated: | ||
**When in Edit mode, the add-on editor should have Seven buttons: "Test", "Download", "Save", "Copy", "Error Console", "Revision", "Properties". | **When in Edit mode, the add-on editor should have Seven buttons: "Test", "Download", "Save", "Copy", "Error Console", "Revision", "Properties". | ||
**When in View mode, the add-on editor should have Five buttons: "Test", "Download", "Copy", "Revision", "Properties". | **When in View mode, the add-on editor should have Five buttons: "Test", "Download", "Copy", "Revision", "Properties". | ||
**When in Edit mode, the library editor should have "Save", "Copy", "Revision","Error Console", "Properties" buttons. | **When in Edit mode, the library editor should have "Save", "Copy", "Revision","Error Console", "Properties" buttons. | ||
**When in View mode, the library editor should have "Copy", "Revision", "Properties" buttons.<br> | **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. | **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> | ||
**The revision should change when the user adds/removes libs(modules)/data(attachments) and libraries. | **<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 "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.) | **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 39: | ||
**A new revision should be generated when the user saves after making changes to the existing addon code. | **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> | **The code for the add-on library should be saved when the save button is pressed.<br> | ||
**<font color=" | **<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> | ||
**< | **<font color="Red">You should be able to edit the name of the Lib(module) by clicking on the pencil like button besides the name.</font> | ||
**<font color="Red">The revision should also be updated when you edit the name of the lib(module)</font> | |||
**<font color="Red">You should be able to edit the name of the Data(attachments) by clicking on the pencil like button besides the name.</font> | |||
**< | **<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> | ||
** You should be able to add a file successfully. | **<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> | ||
** You should be able to upload an attachment using an external URL. | |||
** 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. | |||
*Manual(in-litmus): | *Manual(in-litmus): | ||
**The user should be able to select the entire text present in the text editor. | |||
**The user should be able to perform copy/paste functionality in the text editor. | |||
**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 | **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 pressed button again will uninstall the addon and the button will be released. | ||
**Clicking on the "Download" button should generate an XPI file. | **Clicking on the "Download" button should generate an XPI file. | ||
** | **The user should be able to add attachments ('Data' button on the page). | ||
**Adding attachments should update the revision number of the current addon. | **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 | **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) | ||
**If the user is in the "View" mode, the text attachments should *NOT* be editable. | **If the user is in the "View" mode, the text attachments should *NOT* be editable. | ||
==My account page== | ==My account page== | ||