Tags:
, view all tags

CREAM client testsuite

A test suite for detailed testing of the command line interface to submit to a CREAM CE.

Developers: Alessio Gianelle, Paolo Andreetto, Sara Bertocco

Location: org.glite.testsuites.ctb/CREAM/CREAM-cli

The test suite covers all the glite-ce-* available commands:

  • glite-ce-allowed-submission
  • glite-ce-delegate-proxy
  • glite-ce-disable-submission
  • glite-ce-enable-submission
  • glite-ce-get-cemon-url
  • glite-ce-job-cancel
  • glite-ce-job-lease
  • glite-ce-job-list
  • glite-ce-job-purge
  • glite-ce-job-resume
  • glite-ce-job-status
  • glite-ce-job-submit
  • glite-ce-job-suspend
  • glite-ce-proxy-renew

The main goal of this testsuite is to check the behaviour of each of the commands listed above, with different meaningful options for every command (options such as help, version and debug are not considered). Testing the behaviour of the service is out of the scope of this suite, the result of the operation on the server side is not considered, nevertheless the command must be able to manage correctly any result reported by the service.

Every command handles a large number of faults and errors reported by the service, reproducing all these errors for each test is not viable; the aim of this suite is to check just the fault handling so where it is possible a single fault, representing a class of errors, is generated and tested.

In several cases the test for a client command requires the execution of another one first, with a well defined set of options, in order to prepare the environment for the test. The latter should be considered as "already tested", so the certifier should follow a specific order in the execution of the testsuite. Each test reports the list of prerequisites.

Most of the scripts contained into the testsuite require the submission of one or more jobs, in general for these submissions a very simple JDL file is used (example.jdl), the executable defined into this jdl is a just simple "sleep" with no ISB/OSB movement.

CREAM-cli-delegation.sh

This test performs several delegation calls on the server (command glite-ce-delegate-proxy) with any combination of --logfile and --conf options; then it tries to re-delegate the same ID in order to generate a fault on the server side.

CREAM-cli-delegation-renew.sh

This test performs a renewal of a proxy delegated on the server side (command glite-ce-proxy-renew) with any combination of --logfile and --conf options and tries a renewal of an missing proxy in order to test the fault handling. Prerequisites: CREAM-cli-delegation.sh

CREAM-cli-job-submit.sh

This test carries out several submissions (command glite-ce-job-submit) with:
  • --autm-delegation
  • --delegationid the delegation ID is given by previously calling the delegation operation
  • --output writing the job ID on a newly created file first and then appending the output on an existing one
  • --logfile
  • --conf

Prerequisites: CREAM-cli-delegation.sh

CREAM-cli-job-status-simple.sh

This script tests the command glite-ce-job-status:
  • TEST 1: submit a job and then retrieve its status
  • TEST 2: submit a job which surely failed. Check if the final status is the ones expected
  • TEST 3: check the status of a job setting log level to 1 (option --level 1):
  • TEST 4: check the status of a job setting log level to 2 (option --level 2)
  • TEST 5: check if the option --input works
  • TEST 6: check if the --conf option works
  • TEST 7: save info into a logfile to check if --debug and --logfile options work

Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-job-status-filtered.sh

This script tests the "filtered" options of the command glite-ce-job-status:
  • TEST 1: check if the --from option works:
  • TEST 2: check the --from and --to options together
  • TEST 3: check if the --status option works (using REALLY-RUNNING)
  • TEST 4: check if the --status option works (using DONE-OK)
  • TEST 5: check if the --all option works
  • TEST 6: check the requirements of the --all option (3 cases)

Prerequisites: CREAM-cli-job-submit.sh, CREAM-cli-job-status-simple.sh

CREAM-cli-job-cancel.sh

This test interrupts the execution of one or more existing jobs (command glite-ce-job-cancel) specifying:
  • the ID of a submitted job
  • --all options

Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-job-suspend.sh

This test suspends the execution of one or more existing jobs (command glite-ce-job-suspend) specifying:
  • the ID of a submitted job
  • --all options

Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-job-resume.sh

This test resumes the execution of one or more previously suspended jobs (command glite-ce-job-resume) specifying:
  • the ID of a submitted job
  • --all options

Prerequisites: CREAM-cli-job-suspend.sh

CREAM-cli-job-purge.sh

This script tests the command glite-ce-job-purge:
  • TEST 1: purge a finished job
  • TEST 2: try to purge a running job
  • TEST 3: try to purge again a previous purged job
  • TEST 4: purge more finished jobs
  • TEST 5: purge more jobs taking jobIDs from a file (--input option)
  • TEST 6: check if the --all option works
  • TEST 7: check the requirements of the --all option (3 cases)
  • TEST 8: check if the --conf option works
  • TEST 9: save info into a logfile to check if --debug and --logfile options work

Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-job-list.sh

This script tests the command glite-ce-job-list:
  • TEST 1: check if the command returns the right number of jobs
  • TEST 2: check if the --output option works
  • TEST 3: check if the --conf option works
  • TEST 4: save info into a logfile to check if --debug and --logfile options work

Prerequisites: CREAM-cli-job-submit.sh, CREAM-cli-job-status.sh

CREAM-cli-submission-management.sh

This script tests checks the command glite-ce-allowed-submission:
  • TEST 1: check if the submissions to the CE are allowed
  • TEST 2: check if the --conf option works
  • TEST 3: save info into a logfile to check if --debug and --logfile options work

The others two management commands glite-ce-enable-submission and glite-ce-disable-submission should be test only via a "cream super-users"; so they are not considered.

CREAM-cli-get-cemon-url.sh

This script tests the command glite-ce-get-cemon-url:
  • TEST 1: check if the command returns a valid url
  • TEST 2: check if the --conf option works
  • TEST 3: save info into a logfile to check if --debug and --logfile options work

-- AlessioGianelle - 03 Jun 2008

Edit | Attach | PDF | History: r22 | r16 < r15 < r14 < r13 | Backlinks | Raw View | More topic actions...
Topic revision: r14 - 2008-06-11 - AlessioGianelle
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback