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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 9: Line 9:
<u>'''''configurationAMO''''':</u>  
<u>'''''configurationAMO''''':</u>  


This file is not available on SVN for viewing. It contains tuples/associative arrays of the following:<br>
This file is not available on SVN for viewing. It contains tuples/associative arrays of the following:<br>  


1. 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>
1. 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'}.


2. 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>
 
2. 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>
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>

Revision as of 22:24, 14 April 2010

Config-file documentation

We have 3 configuration files that we use in our automation test cases:

  1. configurationAMO
  2. browserConfig (will be renamed to TCParameters)
  3. GridConnection

configurationAMO:

This file is not available on SVN for viewing. It contains tuples/associative arrays of the following:

1. 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

self.objAMOfunc.login('userNonAdm' sel)

2. Different add-ons. If you want to use a specific add-on then it should be added to the addons array in this file.

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)

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Execution/Web_Testing/Docs/Automation/Testcases/ConfigFiles&oldid=215907"