Changes between Version 1 and Version 2 of BluePrint/Testing/EdenTest


Ignore:
Timestamp:
03/18/14 15:02:27 (11 years ago)
Author:
Arnav Sharma
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BluePrint/Testing/EdenTest

    v1 v2  
    33
    44== Introduction ==
    5 [[BR]]
    6 
    75Creating an automated testing suite using [http://robotframework.org/ Robot Framework] which is configurable, easy to write, easy to maintain and provides in depth logs and reports.[[BR]]
    86
    … …  
    1513
    1614[[BR]]
    17 This will add value to Sahanna as it will provide a handy and usable tool to script and run tests, to diagnose failures and to empower people to use and maintain the test suite
     15This will add value to Sahanna as it will provide a handy and usable tool to script and run tests, to diagnose failures and to empower people to use and maintain the test suite.
    1816
    1917
    20 == Stakeholders == [[BR]]
    21 
     18== Stakeholders ==
    2219* Developers - They will be the users as well as maintainers of the suite.
     20* People using Sahana Eden - They can see which all functionalities are working as expected. 
    2321
    2422== User Stories ==
    25 <http://en.wikipedia.org/wiki/User_story>
    26 <A good User Story should answer the following questions:>
    27 <* Who the user is>
    28 <* What they want the solution to do for them?>
    29 <* Why they want it to do that? (goal)>
    30 <eg. A <type of user> wants the solution to <do something for them> so that <can achieve a goal>.>
     23* A developer can use the suite to confirm that the system does what users are expecting it to and get quality in-depth report and logs to help fix the functionalities that are not behaving as expected.
    3124
    3225== Requirements ==
    33 <Group requirements in subsections, e.g.,, etc.>
    34 <http://en.wikipedia.org/wiki/Requirements_analysis requirements>
    35 <Identify different types of requirements:>
    3626=== Functional ===
     27* Detailed reports and logs. It should provide
     28 * Easy to understand
     29 * Tickets
     30 * Screenshots
     31 * Tracebacks
     32 * Summary reports
     33 * Logs of actions
     34* The tests should give immediate feedback.
     35* Complete system testing[?].
     36* Ability to add a single test as well as group of tests.
     37* Ability to group tests by template and functionality.
     38
    3739=== Non-functional ===
    3840http://en.wikipedia.org/wiki/Non-functional_requirements