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 27: Line 27:
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>  


<br>
<br>  


<u>'''borwserConfig (TCParameters):'''</u><br>
<u>'''borwserConfig (TCParameters):'''</u><br>  


TCParameters has variables defined with values that are required to run a test case. We will have 3 copies of TCParameters, one for Smoke Tests suite, one for Basic Functional Tests suite &amp; one for Full functional tests.<br>
TCParameters has variables defined with values that are required to run a test case. We will have 3 copies of TCParameters, one for Smoke Tests suite, one for Basic Functional Tests suite &amp; one for Full functional tests.<br>  


Some of the variables defined here are: <br>
Some of the variables defined here are: <br>  


# limits for processing loops<br>&nbsp;maxCategories = 3 # maximum number of categories checked in test case<br>&nbsp;maxItemsPerPage = 10 # maximum number of items (ex: personas, add-ons) checked per page<br>&nbsp;# sortOption and sortOptionControl is being replaced by page specific options.<br>&nbsp;sortOption = '' # sort option parameter for a test function. possible values listed in test suite<br>&nbsp;sortOptionControl = '' # sort option control to select, if script handles multiple. values listed in test suite<br>&nbsp;# list sort and filter options<br>&nbsp;AMOhomePageSortOptions = ('recommended', 'popular', 'added', 'updated')<br>&nbsp;AMOhomePageSort = AMOhomePageSortOptions[0] <br>
*limits for processing loops
*&nbsp;maxCategories = 3 # maximum number of categories checked in test case
*&nbsp;maxItemsPerPage = 10 # maximum number of items (ex: personas, add-ons) checked per page
*&nbsp;# sortOption and sortOptionControl is being replaced by page specific options.
*&nbsp;sortOption = ''# sort option parameter for a test function. possible values listed in test suite<br>''
*''&nbsp;sortOptionControl = '' # sort option control to select, if script handles multiple. values listed in test suite
*&nbsp;# list sort and filter options
*&nbsp;AMOhomePageSortOptions = ('recommended', 'popular', 'added', 'updated')
*&nbsp;AMOhomePageSort = AMOhomePageSortOptions[0] <br>


Depending on the kind of test suite, the values will differ. For e.g. maxCategories = 1 (for Smoke Test Suite); maxCategories = 3 (for BFT Suite); maxCategories = all (for FFT); <br>
Depending on the kind of test suite, the values will differ. For e.g. maxCategories = 1 (for Smoke Test Suite); maxCategories = 3 (for BFT Suite); maxCategories = all (for FFT); <br>  


<br>
<br>  


<br>
<br>  


<br>
<br>  


<br>
<br>

Revision as of 00:38, 15 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'}.

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)


borwserConfig (TCParameters):

TCParameters has variables defined with values that are required to run a test case. We will have 3 copies of TCParameters, one for Smoke Tests suite, one for Basic Functional Tests suite & one for Full functional tests.

Some of the variables defined here are:

  • limits for processing loops
  •  maxCategories = 3 # maximum number of categories checked in test case
  •  maxItemsPerPage = 10 # maximum number of items (ex: personas, add-ons) checked per page
  •  # sortOption and sortOptionControl is being replaced by page specific options.
  •  sortOption = # sort option parameter for a test function. possible values listed in test suite
  •  sortOptionControl = # sort option control to select, if script handles multiple. values listed in test suite
  •  # list sort and filter options
  •  AMOhomePageSortOptions = ('recommended', 'popular', 'added', 'updated')
  •  AMOhomePageSort = AMOhomePageSortOptions[0]

Depending on the kind of test suite, the values will differ. For e.g. maxCategories = 1 (for Smoke Test Suite); maxCategories = 3 (for BFT Suite); maxCategories = all (for FFT);