Service Discovery Test Plan
Service Description
Service Discovery is one of the SAGA APIs. The tests described here are specific to the gLite adapter. It is made up of two parts. SD which is described in the OGF document
http://www.gridforum.org/documents/GFD.144.pdf
and the Information System Navigator (ISN). SD provides basic search mechanisms for a service and completely hides the information system - and its schema. This means that users of this API will not be aware of the move to GLUE-II. ISN on the other hand does expose the schema and allows navigation between the entities as described in the GLUE document. It can be configured to support any schema; configurations for GLUE-I and GLUE-II are provided. APIs are offered in C++ and Java. There is also a C API - however this is ad-hoc as OGF has not yet defined any C bindings. In addition there is a command line tool - saga-sd. This tool is currently packaged with the gLite adapter but it will be migrated to the SAGA engine as it has no adapter dependencies. A web tool will be written to offer a user friendly view of both tools.
Features/Scenarios to be tested
For all RPMs
File layout
- Check that the files in the rpm are in sensible places
SD - C++ adapter
This is the C++ API for service discovery.
Documentation
- There should be doxygen output
- There should be a user manual
- Examples should be provided and should run according to the documentation
Functionality testing
The saga-sd tool will be used as it is able to exploit all the features of the API except for the get_related_services call. This will be tested via the Java API as it makes call to the C++ API.
- Check that all valid combinations of parameters are tried. A wide range of filter expressions will be checked.
- Check that bad input produces an acceptable error message for a range of invalid parameters.
SD - Java adapter
This is the Java API for service discovery.
Documentation
- There should be javadoc output
- There should be a user manual
- Examples should be provided and should run according to the documentation
Functionality testing
- Check that all valid combinations of parameters are tried. A wide range of filter expressions will be checked.
- Check that bad input produces an acceptable error message for a range of invalid parameters.
SD - saga-sd
This is the cli for service discovery.
Documentation
- There should be a man page
- The tool should support -h and --help
Functionality testing
- Check that all valid combinations of parameters are tried. A wide range of filter expressions will be checked.
- Check that bad input produces an acceptable error message for a range of invalid parameters.
ISN - C++ adapter
This is the C++ API for the Information Service Navigator
Documentation
- There should be doxygen output
- There should be a user manual
- Examples should be provided and should run according to the documentation
Functionality testing
The saga-isn tool will be used as it is able to exploit all the features of the API.
- Check that all valid combinations of parameters are tried. A wide range of filter expressions will be checked.
- Check that bad input produces an acceptable error message for a range of invalid parameters.
ISN - Java adapter
This is the Java API for the Information Service Navigator
Documentation
- There should be javadoc output
- There should be a user manual
- Examples should be provided and should run according to the documentation
Functionality testing
- Check that all valid combinations of parameters are tried. A wide range of filter expressions will be checked.
- Check that bad input produces an acceptable error message for a range of invalid parameters.
ISN - saga-isn
This is the cli for the Information Service Navigator
Documentation
- There should be a man page
- The tool should support -h and --help
Functionality testing
- Check that all valid combinations of parameters are tried. A wide range of filter expressions will be checked.
- Check that bad input produces an acceptable error message for a range of invalid parameters.
SD/ISN - Portal
This provides access to both SD and ISN as is designed to be very user friendly.
Documentation
- The tool should not have any external documentation but it should be self evident how to use it.
Functionality testing
- Make a manual check that it responds rapidly
- Make a manual check that it is intuitive (probably involving those with no previous exposure to this tool)
- Ensure that it offers complete functionality of the underlying tools
- Try to break it
--
AntonyWilson - 13-Nov-2009
Topic revision: r5 - 2009-11-19
- unknown