Changes between Version 12 and Version 13 of BluePrint/Testing/TestSuite

Timestamp:

04/26/13 22:06:25 (12 years ago)

Author:

somayjain

Comment:

--

BluePrint/Testing/TestSuite

@@ -82 +82 @@
 * The general tests run against each and every template where the target functionality is available. For templates where the functionality is not available, the test auto-deactivate.
 
-* There test suite -
+* The test suite -
      1. Provides a set of functions(create, search, edit) which will take the tablename, labels of the field and the record data as input.
      2. Automatically checks the type of field(option, autocomplete, text, date, datetime, etc) being used in the current template and fill the form accordingly.
@@ -125 +125 @@
 * The load tests will test the amount of load Eden can take under normal and peak conditions. So, the load tests should be divided into phases, with each phase incrementally increasing the number of users and requests. Features of Tsung can be used to do this effectively.
 
-==== Module Enabled or Disabled ====
+==== Deactivation of Tests ====
 
 * 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.
@@ -132 +132 @@
 === Technologies ===
 
+==== CI Server ====
+
 *    For setting up the CI Server, some of the technologies which can be used are given here - [http://eden.sahanafoundation.org/wiki/BluePrintTesting#ContinuousIntegration ContinuousIntegration]
-    
-* For Continuous Integration, an instance of Eden can also be used which will enable Scheduling, enable subscription of notifications for test results, can also provide formatted results.
 
-*  For functional tests, currently, Selenium and Smoke Tests are used. The current Selenium tests should be made more robust and they should work across browsers. Currently, there is support for Firefox Webdriver(upto version 16) and Chrome Webdriver. We need to provide support for Safari Webdriver, Opera Webdriver and Internet Explorer Webdriver.
+* The CI Server will run the tests using a cronjob scheduling the shell scripts.
 
+==== Selenium Tests ====
+
+*  For functional tests, Selenium Tests are used. The selenium tests should work across browsers. Currently, there is support for Firefox Webdriver(upto version 16) and Chrome Webdriver. We need to provide support for Safari Webdriver, Opera Webdriver and Internet Explorer Webdriver.
+
+==== Smoke Tests ====
+The Smoke tests visit every link in Eden to check for errors on a page and broken links. For this, twill and mechanize are used.
+ 
+==== Role Tests ====
 * The Role tests(which currently run only on the IFRC template and uses Selenium Unit Test) are to extend to run on multiple templates.
+
+==== Load Tests ====
+
+* Tsung
+
 == Implementation ==
+
+==== Current Implementation ====
 The Seleium tests can be run on mainly IFRC template. With some changes, they can be run on the default template as well. However, they don’t work across templates.
 
 The unit tests expect that some particular modules are enabled in the template. If they are not enabled and unit tests are run in that template, then false negatives are reported.
 
-Current implementation of the selenium tests, smoke tests, role tests can be found here - 
+Current implementation can be found here - 
 
 https://github.com/flavour/eden/tree/master/modules/tests
@@ -155 +170 @@
 
 * Adapt tests to meet needs of evolving CI Server(SysAdmin/ContinuousIntegration). The tests should successfully run on the CI Server both locally and remotely. 
+
+* For Continuous Integration, an instance of Eden can also be used which will enable Scheduling, enable subscription of notifications for test results, can also provide formatted results.
 
 == References ==