451
edits
QA/Jetpack/AddonBuilderTestPlan/Testcases: Difference between revisions
QA/Jetpack/AddonBuilderTestPlan/Testcases (view source)
Revision as of 20:32, 9 November 2010
, 9 November 2010no edit summary
No edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
***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.) | ***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) | ***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 <font color="Blue">libraries</font> | |||
***<font color="Red">A new revision should be generated when the user saves after making changes to the existing addon code.</font> | ***<font color="Red">A new revision should be generated when the user saves after making changes to the existing addon code.</font> | ||
***<font color="Red">The code for the add-on/library should be saved when the save button is pressed.</font><br> | ***<font color="Red">The code for the add-on/library should be saved when the save button is pressed.</font><br> | ||
***<font color="Blue">The SDK version to be used for the current add-on can be changed from the libraries section.</font> | ***<font color="Blue">The SDK version to be used for the current add-on can be changed from the libraries section.</font> | ||
***<font color="Blue">The revision should change when the user adds/removes libraries</font> | ***<font color="Blue">The revision should change when the user adds/removes libraries</font> | ||