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

Timestamp:

04/19/13 04:33:15 (11 years ago)

Author:

somayjain

Comment:

--

BluePrint/Testing/TestSuite

@@ -25 +25 @@
 
 == Requirements ==
-<Group requirements in subsections, e.g.,, etc.>
-<http://en.wikipedia.org/wiki/Requirements_analysis requirements>
-<Identify different types of requirements:>
+
 === Functional ===
 
@@ -34 +32 @@
 *    Automatically Create Dummy Data while testing.
 
-*    Extend Role Tests (Currently is limited to the IFRC roles for RMS)
+*    Extend Role Tests to run on different templates(Currently is limited to the IFRC roles for RMS)
 
 *    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.
 
-*    Clearer Error Messages in a way that anyone can reproduce them.
+*    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.
 
 *    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.
 
-*    Simplify Selenium Tests and make them easier to read and more robust.
+*    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.
 
-*    Adapt tests to meet needs of evolving CI Server(SysAdmin/ContinuousIntegration)
+*    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.
 
 *    Load Tests