wiki:TestAutomation

Test Automation

Date 2009/07/12
Contact(s) Just van den Broecke
Last edited 2009/07/12
Status draft
Assigned to release Release number, to be determined
Resources ??

Overview

Currently there is little to no test automation available in the GeoNetwork trunk. Within specific projects like ESA and 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 GeoServer are also 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.

Proposal Type

  • Type: Core ChangeGuideline and project governance procedures, ...
  • App: GeoNetwork or !Intermap
  • Module: all Services

Just's Bolsena09 presentation, GeoServer test proposal, csiro.au GeoSciML testing for GeoServer

Voting History

  • Vote proposed by X on Y, result was +/-n (m non-voting members).

Motivations

The current GN trunk implementation has no test automation.

Proposal

We have as a start a backport implementation from the Swiss Topo project. We need the following steps: # investigate GeoServer test status and development # investigate/adopt current approaches in the OSS arena # adopt the current test framework

Backwards Compatibility Issues

None (as there was no test automation).

Risks

That we reinvent the testing wheel (hence the investigations proposed)

Participants

  • List of participants and role (if necessary) in current GIP
Last modified 11 years ago Last modified on Jun 11, 2013, 5:09:25 AM

Attachments (1)

Note: See TracWiki for help on using the wiki.