Changes between Version 5 and Version 6 of QA


Ignore:
Timestamp:
01/04/13 04:04:22 (9 years ago)
Author:
Michael Howden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QA

    v5 v6  
    1414== Automated Tests ==
    1515
     16=== Smoke Tests ===
     17Smoke Tests click through on every link within Sahana Eden and can be used to check for errors on pages and broken links. They are a light-weight approach to detecting basic errors, however they do not test form submission or any interaction.
     18To run the Smoke Tests:
     19{{{
     20python web2py.py -S eden -M -R applications/eden/modules/tests/suite.py -A --suite smoke --force-debug --link-depth 16 -V 3
     21}}}
     22''Add details on the dependancies for these''
     23
     24===  Selenium Tests ===
     25Selenium Tests use the [http://seleniumhq.org/docs/03_webdriver.jsp Selenium WebDriver] to simulate user interactions within a browser. They are very thorough as they test interactions in the entire Sahana Eden stack including JS, but can also be fragile (detect false negatives).
     26To run all the Selenium Tests:
     27{{{
     28python web2py.py -S eden -M -R applications/eden/modules/tests/suite.py
     29}}}
     30See: [wiki:QA/Automated/Selenium Automated Tests - Selenium] for more details
     31
    1632=== Unit Tests ===
    17 There are additional unit tests available, which also require running with the IFRC_Train preopulate, 'settings.base.prepopulate = 27':
    18 
    19 To run all unit tests:
     33Unit Tests can be used to test whether specific "Units" of code are working. They are used extensively to test the Sahana Eden "S3" Framework.
     34Unit Tests require running with the IFRC_Train preopulate, 'settings.base.prepopulate = 27':
     35To run all Unit Tests:
    2036{{{
    2137python web2py.py -S eden -M -R applications/eden/modules/unit_tests/suite.py
     
    3652It can be a very powerful development strategy - especially for back-end APIs - to first implement unit test cases for the functionality you intend to implement before actually implementing it. Apart from preventing bugs, this helps you to validate your design against requirements, and to keep the implementation simple and focussed. Additionally, the test cases can be a rich source of code samples how to apply your API methods.
    3753
    38 === Smoke Tests ===
    39 {{{
    40 python web2py.py -S eden -M -R applications/eden/modules/tests/suite.py -A --suite smoke --force-debug --link-depth 16 -V 3
    41 }}}
    42 
    43 ===  Selenium Tests ===
    44 {{{
    45 python web2py.py -S eden -M -R applications/eden/modules/tests/suite.py
    46 }}}
    47 See: [wiki:QA/Automated/Selenium Automated Tests - Selenium] for more details
    48 
    4954===  Role Tests ===
    50 This test is used to check the permissions of user roles. Currently is limited to the IFRC (Red Cross) roles for RMS, but could be extended:
     55Role tests are used to check the permissions of user roles. Currently is limited to the IFRC (Red Cross) roles for RMS, but could be extended:
     56To run the Role Tests:
    5157{{{
    5258python web2py.py -S eden -M -R applications/eden/modules/tests/suite.py -A --suite roles
     
    5460
    5561===  Benchmark Tests ===
    56 The Benchmark Tests are a simple way of measuring the performance
     62The Benchmark Tests are a simple way of measuring the performance of the Sahana Eden "S3" Framework. The result of these tests will give you a measure of the performance relative to the system running them.
     63To run the Benchmark Tests:
    5764{{{
    5865python web2py.py -S eden -M -R applications/eden/modules/unit_tests/s3/benchmark.py
     
    6370
    6471== Continuous Integration (CI)Server ==
     72The CI Server will constantly run all Automated Tests on the latest version of Sahana Eden to detect any defects.
    6573See: SysAdmin/ContinuousIntegration for how we have set up the CI Server and help to find the exact commands to run the tests.
    6674