CREAM Test work plan

Introduction

The CREAM testsuite is a set of python scripts that interacts with the CREAM command line tools in order to perform several functional tests.

Installation and setup

The easiest way to deploy the testsuite is to have a UI node already available, for further details refer to the Generic Installation and Configuration Guide. The testsuite can be installed using yum creating a file in the yum.repos.d directory with the following definition:

[Testsuite]
name=Testsuites
baseurl=http://devel12.cnaf.infn.it:7444/repository/testsuites/
enabled=1

and then running

yum install org.glite.testsuites.cream

Work plan

Testsuite composition

The set of test can be divided into two main categories, according to the type of status detection mechanism for a job:

• with polling (synchronous):
  • cream-test-monitored-cancel
  • cream-test-monitored-lease-expired
  • cream-test-monitored-lease-updated
  • cream-test-monitored-proxy-expired
  • cream-test-monitored-submit
  • cream-test-notified-lease-updated
• with notifications (asynchronous):
  • cream-test-notified-cancel
  • cream-test-notified-lease-expired
  • cream-test-notified-lease-updated
  • cream-test-notified-submit

Proxy management

Each test can be run using an external user voms-proxy or with an internal management of the voms-proxy. The default mechanism is using an external voms-proxy. The external voms-proxy is not renewed by the test, the user is responsible for updating that credential if required in such a way that it does not interfere with tests, for example "renaming" the new proxy into the old one. The external voms-proxy path is defined with the environment variable X509_USER_PROXY, the main default is /tmp/x509_u.