Changes between Version 22 and Version 23 of BluePrint/Testing/TestSuite


Ignore:
Timestamp:
06/04/13 12:55:41 (8 years ago)
Author:
somayjain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Testing/TestSuite

    v22 v23  
    149149* To ensure that tests(role, selenium, smoke) work across templates and do not show false negatives when run on a different template, a check has to be made if the module it is to work on is enabled/disabled. If the module is disabled, then the test should automatically deactivate and an appropriate message should be included in the test report.
    150150
     151==== Remote Tests ====
     152
     153
     154The basic design for Selenium Tests-
     155
     156*    Prerequisite 1: There are some more instances of Eden with varying configurations (template/python version/database type) running on some servers(preferably in local network with the CI Server, as this will increase the speed of handling requests by the CI Server).
     157*    Prerequisite 2: There is an 'testing' instance of Eden running on the CI Server which contains the test suite.
     158*    The 'testing' instance of Eden will shoot the test suite, while changing the base URL in the test suite. The base URL currently is 127.0.0.1. If we change it to the IP address of some of the currently running instances of Eden on other servers, the tests will start running for those servers.
     159*    The above task can be done as a background process on the CI Server or running the tests using [http://selenium-grid.seleniumhq.org/ SeleniumGrid] to run them in parallel.
     160
     161Points 3 and 4 will be done on the CI Server using scripts(python or bash) and it will be built on top of the current test suite, so that we have to change minimal code in the current test suite.
     162
     163For this plan to succeed, we have to make sure that the Selenium tests run independent of the template. For this, I have investigated that some of the reasons why Selenium Tests fail on different templates are -
     164
     165*    Text in Option field does not matches with that given in test data.
     166*    Field type is incorrect. Most common example - autocomplete v/s option.
     167*    Module is disabled.
     168
     169So, the above issues must be handled prior to running the tests remotely.
     170To find the field type, investigating it from the HTML in the test since we wish to run the tests remotely.
     171
     172Once this is done, we have a tests which can run on a class of templates which are not way too much different from default and IFRC templates.
     173
     174So, we run these tests on these templates for the enabled modules.
     175
    151176
    152177=== Technologies ===