QA/Execution/Web Testing/Docs/Automation/Testcases/ConfigFiles: Difference between revisions
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
A sample user array looks like non_adm = {'login':'nonadminuser@example.com', 'pwd':'somepassword', 'fname':'John', 'nick':'john_non_adm'}. | A sample user array looks like non_adm = {'login':'nonadminuser@example.com', 'pwd':'somepassword', 'fname':'John', 'nick':'john_non_adm'}. | ||
So, if you want to acces the user array from AMOfunctions.py then the code would look like:<br> | |||
''user = self.objConfigAMO.getUserInfo(userType) '' | |||
''user = self.objConfigAMO.getUserInfo(userType) '' | |||
and in your test case it would look like:<br> | and in your test case it would look like:<br> | ||
Revision as of 22:35, 14 April 2010
Config-file documentation
We have 3 configuration files that we use in our automation test cases:
- configurationAMO
- browserConfig (will be renamed to TCParameters)
- 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'}.
So, if you want to acces the user array from AMOfunctions.py then 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)