Changes between Version 3 and Version 4 of BluePrint/Testing/TestSuite


Ignore:
Timestamp:
04/19/13 04:33:15 (8 years ago)
Author:
somayjain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Testing/TestSuite

    v3 v4  
    2525
    2626== Requirements ==
    27 <Group requirements in subsections, e.g.,, etc.>
    28 <http://en.wikipedia.org/wiki/Requirements_analysis requirements>
    29 <Identify different types of requirements:>
     27
    3028=== Functional ===
    3129
     
    3432*    Automatically Create Dummy Data while testing.
    3533
    36 *    Extend Role Tests (Currently is limited to the IFRC roles for RMS)
     34*    Extend Role Tests to run on different templates(Currently is limited to the IFRC roles for RMS)
    3735
    3836*    Run Selenium and Smoke tests in multiple templates with multiple user accounts. Ideally, these tests can be run against each and every template where the target functionality is available. For templates where the functionality is not available, the test should auto-deactivate.
    3937
    40 *    Clearer Error Messages in a way that anyone can reproduce them.
     38*    Clearer Error Messages in a way that anyone can reproduce them. The error message will include the traceback and the record information that the test was intended to create/modify/delete so that the user may easily investigate the test.
    4139
    4240*    The CI Server should catch failures in any template. So, it should run tests across templates and include the template name in the aggregated report.
    4341
    44 *    Simplify Selenium Tests and make them easier to read and more robust.
     42*    Simplify Selenium Tests and make them easier to read and more robust. This will involve creating an abstraction for Selenium Tests, such that it takes few minutes to write a test for a new module.
    4543
    46 *    Adapt tests to meet needs of evolving CI Server(SysAdmin/ContinuousIntegration)
     44*    Adapt tests to meet needs of evolving CI Server(SysAdmin/ContinuousIntegration). The tests should successfully run on the CI Server both locally and remotely. As mentioned before, it should then send the results via email.
    4745
    4846*    Load Tests