Changes between Version 2 and Version 3 of TestAutomation


Ignore:
Timestamp:
Jul 13, 2009, 6:42:22 AM (15 years ago)
Author:
just
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TestAutomation

    v2 v3  
    1010== Overview ==
    1111
    12 Currently there is little to no test automation available in the GeoNetwork trunk. Specific projects like for ESA and Swiss Topo have developed test-approaches within their respective sandboxes. It is recognized that there are many forms of testing, for example both "black" and "white (unit)" -box testing. This proposal is about making a start for black box testing the GN protocol APIs using a uniform approach for conformance/performance and stress testing. This uniform approach implies the development of a "test framework" that should facilitate authoring and (automated) execution of tests. Note that other projects like GeoServer, having much more experience e.g. with CITE tests, are also [http://docs.codehaus.org/display/DH/Home considering a similar test approach]. This is also an area where we should work together with the GS team as we have similar requirements.
     12Currently there is little to no test automation available in the GeoNetwork trunk. Within specific projects like [http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/sandbox/3.0.x/ ESA] and [http://tinyurl.com/mbpwbc Swiss Topo] test-approaches have been developed within their respective sandboxes. It is recognized that there are many forms of testing, for example both "black" and "white (unit)" -box testing. This proposal is about making a start for black box testing the GN protocol APIs using a uniform approach for conformance/performance and stress testing. This uniform approach implies the development of a "test framework" that should facilitate authoring and (automated) execution of tests. Note that other "OGC-WS" projects like [http://geoserver.org GeoServer] are also [http://docs.codehaus.org/display/DH/Home considering a similar test approach], evolving their CITE test-approach. This may be an area where GN and GS can work together as we have similar requirements.
    1313
    1414=== Proposal Type ===
    … …  
    1818
    1919=== Links ===
    20  * '''Documents''': Bolsena09 presentation attached below, [http://docs.codehaus.org/display/DH/Home GeoServer test proposal]
     20 * '''Documents''': [http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/trunk/test/readme.txt readme on current trunk implementation], Bolsena09 presentation PDF attached below, [http://docs.codehaus.org/display/DH/Home GeoServer test proposal]
    2121 * '''Email discussions''': [http://tinyurl.com/ntqnsg GN-devel test framework after Bolsena09], [http://bit.ly/3m9VO GeoServer-devel CITE discussion]
    2222 * '''Other wiki discussions''':
    … …  
    3131
    3232== Proposal ==
    33 (To be supplied) As a start user the implementation from the Swiss Topo project (geocat.sh sandbox).
     33We have as a start a [http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/trunk/test/readme.txt backport implementation from the Swiss Topo project].
     34We need the following steps:
     35# investigate GeoServer test status and development
     36# investigate/adopt current approaches in the OSS arena
     37# adopt the current test framework
     38
    3439
    3540=== Backwards Compatibility Issues ===
    … …  
    3742
    3843== Risks ==
     44That we reinvent the testing wheel (hence the investigations proposed)
    3945
    4046== Participants ==