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


Ignore:
Timestamp:
03/19/14 10:39:43 (7 years ago)
Author:
Arnav Sharma
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Testing/EdenTest

    v3 v4  
    4545 * Precise
    4646
    47 === Interoperability ===
    48 <Read the articles again>
     47== Design ==
    4948
    50 === System Constraints ===
    51 
    52 == Design ==
    53 <Where relevant include alternative design options>
    5449=== Testing Architecture ===
    5550[[Image(http://web.iiit.ac.in/~arnav.s/sahana/testingArchitechture.png)]]
    56 === Workflows ===
    57 <Diagrams or Pseudocode>
    58 === Site Map ===
    59 <for User Interface solutions>
    60 === Wireframes ===
    61 <for User Interface solutions>
     51
     52=== Directory Structure ===
     53[[Image(http://web.iiit.ac.in/~arnav.s/sahana/dirStructures.png)]]
     54
     55* Everything is bundled under one directory which can be called '''FunctionalTests'''.
     56 * '''TestRunner.py''' can be used to provide to a wrapper to easily call the testsuite or a group of tests or tests on a particular template through command line arguments.
     57 * '''robot''' contains the implementation and execution aspects of the functional tests using robot framework.
     58  * In the implementation side, all the testsuites are grouped according to the modules inside the '''testsuite''' folder.
     59  * All the resources go to the '''resources''' folder which will have various keywords grouped according to the functionality they serve.
     60  * Inside '''execution''' folder, '''settings''' is holding the specific variable files. It should be noted that especially the settings are only written once in the beginning of the project and are very rarely changed afterwards.
     61  * Inside the lib-folder we check-in our own Test Libraries, but it might also make sense to store ready-made libraries here to ensure they are kept stable.
     62   * '''Eden Test Library''' can be used to implement Eden specific functionalities for eg: a keyword 'Run on templates IFRC default' or 'Not run on templates default' etc. 
     63=== Use Case Diagram ===
     64[[Image(http://web.iiit.ac.in/~arnav.s/sahana/UseCaseDiag.png)]]
    6265=== Technologies ===
     66* [http://robotframework.org/ Robot Framework]
    6367
    6468== Current Implementation ==
    65 <Leave open for a list of existing implementation of this solution in Sahana Eden:>
    66 <*a brief description of the implementation (date/time, name, design options chosen)>
    67 <*a link to the code>
    68 <*list of deployments of the implementation>
    69 <*links to case studies>
    70 <*short analysis of achievements/problems>
    71 
    72 == Planned Implementation ==
    73 <List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on>
     69[https://github.com/nerdis/edentest edentest by nerdis]
    7470
    7571== Future Extensions ==
    76 <List of features which could be included, but are outside of the scope of this extension>
    77 
    78 == Outstanding Questions ==
    79 <Questions about the features or design that haven't been (and need to be) answered>
     72* Robot Framework has a plugin for Jenkins which can then be merged into the CI server.
    8073
    8174== References ==
    82 <Links to external resources>
     75[https://blog.codecentric.de/en/2010/07/how-to-structure-a-scalable-and-maintainable-acceptance-test-suite/ Blog post by Andreas Ebbert-Karroum on How to structure a scalable and maintainable accpetance test suite]
    8376
     77[http://dhemery.com/pdf/writing_maintainable_automated_acceptance_tests.pdf Writing Maintainable Automated Acceptance Tests, Dale H. Emery]
     78
     79[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html Robot Framework User Guide]
    8480----
    8581BluePrint