Service Discovery Test Plan

Service Description

Service Discovery is a client side library to provide an information system (IS) independent abstraction for finding services and discovering their basic attributes. The core component is the C library (glite-service-discovery-api-c), which provides the IS independent interface. In addition there is a command line tool, glite-sd-query using this library (glite-service-disvoery-cli). Service discovery is currently used by the following packages: glite-data-catalog-cli, glite-data-transfer-cli, glite-data-transfer-agents, glite-data-hydra-cli

Testing Service Discovery

Testing of the Service Discovery is divided into two phases. The first phase tests the CLI "glite-sd-query" module that is included in the gLite middleware. The second phase tests the C-API provided in the SD website.

For the CLI tool there are 3 levels of testing that should be performed.

Features/Scenarios to be tested

Command Line Tool

Documentation

  • There should be a man page
  • The tool should support -h and --help

'Binaries and Environmental Variable Existence Test (implemented)'

Test Location: Binaries test(Bash)

Normal workflow - correct input
This tests whether the Service Discovery command line tool exists in the middleware. In addition it tests whether the environmental variables required by the CLI tool are set. Descriptive information is provided to the user whether the CLI tool exists or not and which environmental variables are set/unset.

Pass/Fail Criteria
  • Pass -> The CLI tool exists and all the necessary environmental variables are set
  • Pass -> The CLI tool does not exist or one of the required environmental variables is not set

Error workflow - erroneous input
N/A

'Functional Test (implemented)'

Test Location: Functional test(Bash)

Normal workflow - correct input
This tests whether the Service Discovery command line tool returns the correct output. The script sets the required environmental variables and queries site: CY-01-KIMON for the service: org.glite.wms.WMProxy.

Pass/Fail Criteria
  • Pass -> When a message like the following is returned:
    Name: wmslb101.grid.ucy.ac.cy_org.glite.wms.WMProxy_612498381
    Type: org.glite.wms.WMProxy
    Endpoint: https://wmslb101.grid.ucy.ac.cy:7443/glite_wms_wmproxy_server
    Version: 3.2.1
    Site: CY-01-KIMON
    WSDL: http://trinity.datamat.it/projects/EGEE/WMProxy/WMProxy.wsdl
    VOs: atlas,alice,biomed,cms,see,dteam,ops,geclipse,lhcb,ops.vo.egee-see.org
    
    Service Data:
     Key: glite-info-service_hostname - Value: wmslb101.grid.ucy.ac.cy
     Key: glite-info-service_version - Value: 1.5
     Key: DN - Value: /C=CY/O=CyGrid/O=HPCL/CN=wmslb101.grid.ucy.ac.cy
    

  • Pass -> When an error message is returned.

Error workflow - erroneous input
N/A

'CLI Tool Man page Existence Test (implemented)'

Test Location: CLI Man Page test(Bash)

Normal workflow - correct input
This tests whether the man page for the Service Discovery command line tool exists in the middleware.

Pass/Fail Criteria
  • Pass -> The CLI tool man page exists
  • Pass -> The CLI tool man page does not exist

Error workflow - erroneous input
N/A

C-API

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

  • 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.

Features not to be tested

'Feature Summary'

Description and explanation for not being included in the current test plan

-- NicholasLoulloudes

Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2010-01-21 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback