Tags:
, view all tags

WMS Service test suite

Introduction

The WMS-service testsuite is a set of shell scripts that interacts with the WMS command line tools in order to perform several functional tests.

Location: org.glite.testsuites.ctb/WMS/WMS-service

Developers: Alessio Gianelle

The testsuite should be divided into two parts: the first one is composed by some scripts one for each commands available in the WMS-CLI (glite-wms-job-*), the purpose of these tests is to check every single command and to check if the service reacts as expected; these tests can also be used to check the WMS command line commands. Then there are some general scripts which check singles features of the WMS service.

There are two ways to configure the tests: you can use a configuration file (wms-command.conf) like this one:

### Required parameters
# WMS used for tests
WMS="wms.pd.infn.it"
# LB used in the test
LB="lb.pd.infn.it"
# User VO
VO="dteam"

### Optional parameters
# Default requirements
DEFAULTREQ="other.GlueCEStateStatus == \"Production\""
# Number of retrievals before to stop test (timeout)
NUM_STATUS_RETRIEVALS=100
# Seconds between two retreivals
SLEEP_TIME=30

Or you can set the required parameters through command line options:

 -h          this help
 -l          save output in a file
 -d <level > print verbose messages (level = (1|2|3)
 -i          interactive mode (it asks for proxy pwd)
 -n          nagios mode
 -c <conf>   configuration file
 -W <wms>    WMS host (required if conf file is not used)
 -L <lb>     LB host (required if conf file is not used)
 -C <ce>     CE host
 -v <vo>     User VO (required if conf file is not used)

As you can see there are some required parameters: WMS which is the WMS hostname to test, LB which is the LB hostname and VO which is the name of the user's VO.

To use the WMS service a valid proxy is needed. There are three ways to set it for the testsuite: you can create a valid proxy before execute the testsuite (i.e. the default location pointed by X509_USER_PROXY is used) or you can left the testsuite to create it for you digiting the passphrase in an interactive mode (i.e. use option -i) or setting a default key without password. Note that some tests require the possibility to create limited proxies so they work only in the second case (i.e. if you give to the testsuite the opportunity to create the proxy).

Testsuite description

WMS-command_job-delegate-proxy.sh

This test is intended to verify glite-wms-job-delegate-proxy command

Test the command with these options:

  • --version
  • --logfile
  • --output
  • --endpoint
  • --autm-delegation
success means that command has success, delegation is stored in the WMS and that we are able to submit a job

The following tests are possible only in interactive mode (i.e. use option -i)

  • Delegate a shorter proxy
  • Try to delegate with an expired proxy
  • Try to submit with an expired delegation

Releases and Changelog

Regression tests

Location: http://glite.cvs.cern.ch/cgi-bin/glite.cgi/org.glite.testsuites.ctb/WMS/regression/

To create a regression test please follow this simple rules:

  • Create a description file: <bug number>.txt with this information:
Bug: <put the bug number>
Link: <link to savannah bug page>
Summary: <short description of the bug>
And then a list of actions that should be taken to test the bug.

  • If need create a jdl file: <bug number>.jdl

You can add also this attribute to jdl that could be useful for future checks:

usertags = [ bug = "<put bug number>" ];

  • If need create a bash script file: <bug_number>_exe.sh

You can found also a directory with some example file of data to use as InputSandBox and a directory with not silly executables.

These tests are NOT supposed to be run automatically so some manual intervention should be required also on the WMS machine.

-- AlessioGianelle - 08 Jul 2008

Edit | Attach | PDF | History: r10 | r7 < r6 < r5 < r4 | Backlinks | Raw View | More topic actions...
Topic revision: r5 - 2011-03-03 - AlessioGianelle
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback