451
edits
QA/Jetpack/AddonBuilderTestPlan/Testcases: Difference between revisions
QA/Jetpack/AddonBuilderTestPlan/Testcases (view source)
Revision as of 19:47, 31 January 2011
, 31 January 2011→Editor Page
| Line 29: | Line 29: | ||
**When in Edit mode, the add-on editor should have Six buttons: "Test", "Download", "Save", "Copy", "Revision", "Properties".(change) | **When in Edit mode, the add-on editor should have Six buttons: "Test", "Download", "Save", "Copy", "Revision", "Properties".(change) | ||
**When in View mode, the add-on editor should have Five buttons: "Test", "Download", "Copy", "Revision", "Properties".(change) | **When in View mode, the add-on editor should have Five buttons: "Test", "Download", "Copy", "Revision", "Properties".(change) | ||
**When in Edit mode, the library editor should have "Save", "Copy", "Revision", "Properties" buttons. | **When in Edit mode, the library editor should have "Save", "Copy", "Revision", "Properties" buttons. | ||
**When in View mode, the library editor should have "Copy", "Revision", "Properties" buttons. | **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. | ||
**The user should be able to add/remove Lib(modules) and | **<b>The user should be able to add/remove Lib(modules) and Plugins(libraries) and the list of libs/plugins should be updated.<b> | ||
**The revision should change when the user adds/removes Lib(modules). | **The revision should change when the user adds/removes Lib(modules). | ||
**<font color="Red">The total number of modules should be displayed in the modules section.</font> | **<font color="Red">The total number of modules should be displayed in the modules section.</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.) | ||
**You should *NOT* be able to change the information of the add-on in view source mode.(The Properties button should just display information and no editable fields | **You should *NOT* be able to change the information of the add-on in view source mode.(The Properties button should just display information and no editable fields) | ||
**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. | **The code for the add-on library should be saved when the save button is pressed.<br> | ||
**<font color="Blue">The SDK version to be used for the current add-on can be changed from the plugins(libraries) section.</font> | **<font color="Blue">The SDK version to be used for the current add-on can be changed from the plugins(libraries) section.</font> | ||
**< | **<b>The revision should change when the user adds/removes plugins(libraries)</b> | ||
**<font color="Red">The total number of libraries added should be displayed in the libraries section</font> | **<font color="Red">The total number of libraries added should be displayed in the libraries section</font> | ||
**< | **<b>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)</b> | ||
**The user should be able to select the entire text present in the text editor. | **<b>The user should be able to select the entire text present in the text editor.</b> | ||
**The user should be able to perform copy/paste functionality in the text editor. | **<b>The user should be able to perform copy/paste functionality in the text editor.</b> | ||
**You should be able to edit the name of the Lib(module) by clicking on the pencil like button besides the name. | **<b>You should be able to edit the name of the Lib(module) by clicking on the pencil like button besides the name.</b> | ||
**The revision should also be updated when you edit the name of the lib(module) | **<b>The revision should also be updated when you edit the name of the lib(module)</b> | ||
*Manual(in-litmus): | *Manual(in-litmus): | ||
| Line 53: | Line 53: | ||
**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). | **<b>The user should be able to add attachments ('Data' button on the page).</b> | ||
**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) (new) | **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) (new) | ||