QA/Execution/Web Testing/Docs/Automation/Testcases/ConfigFiles: Difference between revisions

QA/Execution/Web Testing/Docs/Automation/Testcases/ConfigFiles (view source)

Revision as of 22:24, 14 April 2010

20 bytes added , 14 April 2010

no edit summary

Vish moz

169

edits

@@ Line 9: / Line 9: @@
 <u>'''''configurationAMO''''':</u>
 This file is not available on SVN for viewing. It contains tuples/associative arrays of the following:<br>
-. Different user types such as admin user, non-admin user, a user with developer rights, a user with certain addons etc. a sample user array looks like non_adm = {'login':'nonadminuser@example.com', 'pwd':'somepassword', 'fname':'John', 'nick':'john_non_adm'}. In your AMOfunctions.py if you want to access array of a particular user-type , the code would look like: ''user = self.objConfigAMO.getUserInfo(userType) ''and in your test case it would look like<br>
+. Different user types such as admin user, non-admin user, a user with developer rights, a user with certain&nbsp;&nbsp; addons etc.
-self.objAMOfunc.login('userNonAdm' sel) <br>
+A sample user array looks like non_adm = {'login':'nonadminuser@example.com', 'pwd':'somepassword', 'fname':'John', 'nick':'john_non_adm'}.
-. Different add-ons. If you want to use a specific add-on then it should be added to the addons array in this file. <br>
+In your AMOfunctions.py if you want to access array of a particular user-type , the code would look like: ''user = self.objConfigAMO.getUserInfo(userType) ''and in your test case it would look like<br>
+self.objAMOfunc.login('userNonAdm' sel) <br>
+. Different add-ons. If you want to use a specific add-on then it should be added to the addons array in this file. <br>
 Note: It is recommended not to use a specific add-on unless necessary. Currently, our tests picks a random add-on from the home-page if you call the function ''getRandomAddonVersion2(appName, sel) ''<br>