Difference: CreamCli (1 vs. 22)

Revision 222011-02-24 - AlessioGianelle

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="TestWokPlan"
>
>
META TOPICPARENT name="TestPage"
 

CREAM CLI testsuite

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

Revision 212011-02-10 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM CLI testsuite

Line: 21 to 21
 
  • glite-ce-job-list
  • glite-ce-allowed-submission
  • glite-ce-event-query
Added:
>
>
  • glite-ce-job-output
  These commands could not be tested without adding the test user as a CREAM "super-user":
  • glite-ce-disable-submission
Line: 57 to 58
  The only required parameter is CREAM.
Changed:
<
<
Every scripts accept the --debug (or -d) option which overwrites the DEBUG parameter setting it to value 1 (some debug informations should be printed in standard output).
>
>
Every scripts accept the --debug (or -d) option which overwrites the DEBUG parameter setting it to value 1 (some debug informations should be printed in standard output and the working directory is not cleanup at the end of the test).
 

CREAM-cli-service-info.sh

Line: 182 to 184
 Prerequisites: CREAM-cli-job-submit.sh, CREAM-cli-job-status.sh, CREAM-cli-job-purge.sh

CREAM-cli-submission-management.sh

Changed:
<
<
This script tests checks the command glite-ce-allowed-submission:
>
>
This script tests 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
Added:
>
>

CREAM-cli-job-output.sh

This script tests the command glite-ce-job-output: test success if all the required (3) files are retrieved, and if the standard output (out.txt) contains the hostname of the worker node where job has been run.
  • TEST 1: output retrieve without option
  • TEST 2: output retrieve with --dir option
  • TEST 3: check --noint option
  • TEST 4: check if --input option works
  • TEST 5: check if command works with multiple JOBID

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

 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.

Revision 202010-03-19 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM CLI testsuite

Line: 9 to 9
 Location: org.glite.testsuites.ctb/CREAM/CREAM-cli

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

Added:
>
>
  • glite-ce-service-info
 
  • glite-ce-delegate-proxy
  • glite-ce-proxy-renew
  • glite-ce-job-submit
Line: 58 to 59
  Every scripts accept the --debug (or -d) option which overwrites the DEBUG parameter setting it to value 1 (some debug informations should be printed in standard output).
Added:
>
>

CREAM-cli-service-info.sh

This script tests the command glite-ce-service-info:
  • TEST 1: check option --version
  • TEST 2: check the service info using various log level
  • TEST 3: check if the --conf option works
  • TEST 4: save info into a logfile to check if --debug and --logfile options work
 

CREAM-cli-delegation.sh

This script tests the command glite-ce-delegate-proxy:
  • TEST 1: delegate a proxy specifying CREAM URL and delegation ID

Revision 192010-03-16 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM CLI testsuite

Line: 19 to 19
 
  • glite-ce-job-purge
  • glite-ce-job-list
  • glite-ce-allowed-submission
Added:
>
>
  • glite-ce-event-query
  These commands could not be tested without adding the test user as a CREAM "super-user":
  • glite-ce-disable-submission
Line: 162 to 163
  Prerequisites: CREAM-cli-job-submit.sh, CREAM-cli-job-status.sh
Added:
>
>

CREAM-cli-event-query.sh

This script tests the command glite-ce-event-query:
  • TEST 1: check if the command retrieves all pending events
  • TEST 2: check if the command retrieves the last events
  • 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-job-purge.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

Revision 182010-03-15 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM CLI testsuite

Line: 19 to 19
 
  • glite-ce-job-purge
  • glite-ce-job-list
  • glite-ce-allowed-submission
Deleted:
<
<
  • glite-ce-get-cemon-url
  These commands could not be tested without adding the test user as a CREAM "super-user":
  • glite-ce-disable-submission
Line: 172 to 171
 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.
Deleted:
<
<

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 \ No newline at end of file

Revision 172009-03-04 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM CLI testsuite

Line: 120 to 120
  Prerequisites: CREAM-cli-job-submit.sh
Changed:
<
<

CREAM-cli-job-suspend.sh

>
>

CREAM-cli-job-suspend.sh (it works only with some batch systems)

 This script tests the command glite-ce-job-suspend:
Changed:
<
<
  • TEST 1: submit and then suspend a running job (it works only with some batch systems)
>
>
  • TEST 1: submit and then suspend a running job
 
  • TEST 2: check if --all option works
  • TEST 3: try to suspend a terminated job
  • TEST 4: save info into a logfile to check if --debug and --logfile options work
Line: 130 to 130
  Prerequisites: CREAM-cli-job-submit.sh
Changed:
<
<

CREAM-cli-job-resume.sh

>
>

CREAM-cli-job-resume.sh (it works only with some batch systems)

 This script tests the command glite-ce-job-resume:
  • TEST 1: submit, suspend and then resume a running job
  • TEST 2: check if --all option works

Revision 162008-06-16 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM CLI testsuite

Line: 33 to 33
  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.
Changed:
<
<
To execute the tests you have to define some parameters in the configuration file (test.conf):
>
>
To execute the tests you need a valid voms proxy accepted by the resource, and you have to define some parameters in the configuration file (test.conf):
 
# Configuration file for the Cream-CLI test suite

Revision 152008-06-12 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"
Changed:
<
<

CREAM client testsuite

>
>

CREAM CLI testsuite

  A test suite for detailed testing of the command line interface to submit to a CREAM CE.
Line: 9 to 9
 Location: org.glite.testsuites.ctb/CREAM/CREAM-cli

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

Deleted:
<
<
  • glite-ce-allowed-submission
 
  • glite-ce-delegate-proxy
Changed:
<
<
  • 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-proxy-renew
 
  • glite-ce-job-submit
Added:
>
>
  • glite-ce-job-status
  • glite-ce-job-cancel
 
  • glite-ce-job-suspend
Changed:
<
<
  • glite-ce-proxy-renew
>
>
  • glite-ce-job-resume
  • glite-ce-job-purge
  • glite-ce-job-list
  • glite-ce-allowed-submission
  • glite-ce-get-cemon-url

These commands could not be tested without adding the test user as a CREAM "super-user":

  • glite-ce-disable-submission
  • glite-ce-enable-submission
  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.

Changed:
<
<
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.
>
>
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.
Added:
>
>
To execute the tests you have to define some parameters in the configuration file (test.conf):
# Configuration file for the Cream-CLI test suite

# *REQUIRED*
# Set this to the CREAM resource to test
CREAM="<set this to a valid resource>"

# Optional
# Print debug messages (it could be overwritten by command line option -d)
DEBUG=0 # 0 or 1

# Define "waiting loop" parameters (after NUM_STATUS_RETRIEVALS*SLEEP_TIME
# seconds the job id considered lost and the test failed)
NUM_STATUS_RETRIEVALS=40
SLEEP_TIME=5

# A jdl file used to test commands
JDLFILE=$(dirname $0)/example.jdl

The only required parameter is CREAM.

Every scripts accept the --debug (or -d) option which overwrites the DEBUG parameter setting it to value 1 (some debug informations should be printed in standard output).

 

CREAM-cli-delegation.sh

Changed:
<
<
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.
>
>
This script tests the command glite-ce-delegate-proxy:
  • TEST 1: delegate a proxy specifying CREAM URL and delegation ID
  • TEST 2: re-delegate the proxy specified in the previous test
  • TEST 3: check if the --conf option works
  • TEST 4: save info into a logfile to check if --debug and --logfile options work
 

CREAM-cli-delegation-renew.sh

Changed:
<
<
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.
>
>
This script tests the command glite-ce-proxy-renew:
  • TEST 1: renew a proxy specifying CREAM URL and delegation ID
  • TEST 2: try to renew a missing proxy
  • 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-delegation.sh

CREAM-cli-job-submit.sh

Changed:
<
<
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
>
>
This script tests the command glite-ce-job-submit:
  • TEST 1: submit a job without mandatory option: --autm-delegation
  • TEST 2: submit a job with automatic delegation (option --autm-delegation)
  • TEST 3: submit a job using a previously delegated credentials (options --delegationId)
  • TEST 4: check if the option --output works
  • TEST 5: check if using again option --output the new joid is append to the existing file
  • 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-delegation.sh
Line: 75 to 110
 Prerequisites: CREAM-cli-job-submit.sh, CREAM-cli-job-status-simple.sh

CREAM-cli-job-cancel.sh

Changed:
<
<
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
>
>
This script tests the command glite-ce-job-cancel:
  • TEST 1: submit and then cancel a running job
  • TEST 2: try to cancel a terminated job
  • TEST 3: check if the --all option works
  • TEST 4: check the requirements of the --all option (3 cases)
  • TEST 5: check if the --conf option works
  • TEST 6: save info into a logfile to check if --debug and --logfile options work
  Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-job-suspend.sh

Changed:
<
<
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
>
>
This script tests the command glite-ce-job-suspend:
  • TEST 1: submit and then suspend a running job (it works only with some batch systems)
  • TEST 2: check if --all option works
  • TEST 3: try to suspend a terminated job
  • TEST 4: save info into a logfile to check if --debug and --logfile options work
  • TEST 5: check if the --conf option works
  Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-job-resume.sh

Changed:
<
<
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
>
>
This script tests the command glite-ce-job-resume:
  • TEST 1: submit, suspend and then resume a running job
  • TEST 2: check if --all option works
  • TEST 3: try to resume a running job
  • TEST 4: save info into a logfile to check if --debug and --logfile options work
  • TEST 5: check if the --conf option works
 
Changed:
<
<
Prerequisites: CREAM-cli-job-suspend.sh
>
>
Prerequisites: CREAM-cli-job-submit.sh, CREAM-cli-job-suspend.sh
 

CREAM-cli-job-purge.sh

This script tests the command glite-ce-job-purge:

Revision 142008-06-11 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 52 to 52
 Prerequisites: CREAM-cli-delegation.sh

CREAM-cli-job-status-simple.sh

Changed:
<
<
This test retrieves the status of an existing job (command glite-ce-job-status) with different verbosity levels (--level option)
  • --input check the status of a set of jobs using a file of jobids
  • --conf
  • --logfile
>
>
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

Changed:
<
<
This test retrieves the status of a group of existing jobs (command glite-ce-job-status) specifying:
  • --all
  • any combination of --status, --from, --to options
>
>
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)
 
Changed:
<
<
Prerequisites: CREAM-cli-job-submit.sh
>
>
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:
Line: 81 to 89
 Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-job-resume.sh

Changed:
<
<
This test resumes the execution of one or more previously suspended jobs (command glite-ce-job-suspend) specifying:
>
>
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

Changed:
<
<
This test removes any data from the service about one or more jobs (command glite-ce-job-purge) specifying:
  • the ID of a submitted job
  • --all options
>
>
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

Changed:
<
<
This test prints the list of submitted jobs (command glite-ce-job-list) with any combination of --logfile and --conf options.
>
>
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
 
Changed:
<
<
Prerequisites: CREAM-cli-job-submit.sh
>
>
Prerequisites: CREAM-cli-job-submit.sh, CREAM-cli-job-status.sh
 

CREAM-cli-submission-management.sh

Changed:
<
<
This test checks the behaviour of the command for submission management glite-ce-allowed-submission.
>
>
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
 
Changed:
<
<
The others two management commands glite-ce-enable-submission and glite-ce-disable-submission should be test only via a "super-users".
>
>
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

Changed:
<
<
This test retrieves the URL of cemonitor (command glite-ce-get-cemon-url) with any combination of --logfile and --conf options.
>
>
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

Revision 132008-06-11 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 100 to 100
 Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-submission-management.sh

Changed:
<
<
This test checks the behaviour of the commands for submission management (glite-ce-enable-submission, glite-ce-disable-submission, glite-ce-allowed-submission)
>
>
This test checks the behaviour of the command for submission management glite-ce-allowed-submission.
 
Added:
>
>
The others two management commands glite-ce-enable-submission and glite-ce-disable-submission should be test only via a "super-users".
 

CREAM-cli-get-cemon-url.sh

This test retrieves the URL of cemonitor (command glite-ce-get-cemon-url) with any combination of --logfile and --conf options.

Revision 122008-06-10 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 55 to 55
 This test retrieves the status of an existing job (command glite-ce-job-status) with different verbosity levels (--level option)
  • --input check the status of a set of jobs using a file of jobids
  • --conf
Added:
>
>
  • --logfile
  Prerequisites: CREAM-cli-job-submit.sh

Revision 112008-06-09 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 54 to 54
 

CREAM-cli-job-status-simple.sh

This test retrieves the status of an existing job (command glite-ce-job-status) with different verbosity levels (--level option)
  • --input check the status of a set of jobs using a file of jobids
Added:
>
>
  • --conf
  Prerequisites: CREAM-cli-job-submit.sh

Revision 102008-06-09 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 53 to 53
 

CREAM-cli-job-status-simple.sh

This test retrieves the status of an existing job (command glite-ce-job-status) with different verbosity levels (--level option)
Added:
>
>
  • --input check the status of a set of jobs using a file of jobids
  Prerequisites: CREAM-cli-job-submit.sh

Revision 92008-06-06 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 27 to 27
  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.
Changed:
<
<
Every command handles a large number of fault 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.
>
>
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.

Revision 82008-06-06 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 48 to 48
 
  • --output writing the job ID on a newly created file first and then appending the output on an existing one
  • --logfile
  • --conf
Deleted:
<
<
  • --ftp-streams this option could be ignored
Fill in the JDL section.
  Prerequisites: CREAM-cli-delegation.sh

Revision 72008-06-05 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 32 to 32
 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.
Changed:
<
<
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: JDLfilename
>
>
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.
Line: 72 to 72
  Prerequisites: CREAM-cli-job-submit.sh
Added:
>
>

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-suspend) specifying:
  • the ID of a submitted job
  • --all options

Prerequisites: CREAM-cli-job-suspend.sh

 

CREAM-cli-job-purge.sh

This test removes any data from the service about one or more jobs (command glite-ce-job-purge) specifying:
  • the ID of a submitted job

Revision 62008-06-04 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 35 to 35
 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: JDLfilename

CREAM-cli-delegation.sh

Changed:
<
<
This test performs several delegation calls on the server (command glite-ce-delegate-proxy) with any combination of --logfile and --conf options.
>
>
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.
Line: 85 to 85
 Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-submission-management.sh

Changed:
<
<
This test check the behaviour of the commands for submission management (glite-ce-enable-submission, glite-ce-disable-submission, glite-ce-allowed-submission)
>
>
This test checks the behaviour of the commands for submission management (glite-ce-enable-submission, glite-ce-disable-submission, glite-ce-allowed-submission)

CREAM-cli-get-cemon-url.sh

This test retrieves the URL of cemonitor (command glite-ce-get-cemon-url) with any combination of --logfile and --conf options.
  -- AlessioGianelle - 03 Jun 2008 \ No newline at end of file

Revision 52008-06-04 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 84 to 84
  Prerequisites: CREAM-cli-job-submit.sh
Added:
>
>

CREAM-cli-submission-management.sh

This test check the behaviour of the commands for submission management (glite-ce-enable-submission, glite-ce-disable-submission, glite-ce-allowed-submission)
 -- AlessioGianelle - 03 Jun 2008

Revision 42008-06-04 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 27 to 27
  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.
Added:
>
>
Every command handles a large number of fault 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.
Line: 35 to 37
 

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.
Added:
>
>

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

Revision 32008-06-03 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

CREAM client testsuite

Line: 26 to 26
 
  • 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.

Changed:
<
<
In several cases one script requires the execution of another one first in order to prepare the environment for the test; as the test should be self-contained, the former calls the latter inside with a well defined set of options, for example CREAM-cli-job-submit.sh calls CREAM-cli-delegation.sh.
>
>
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: JDLfilename

 

CREAM-cli-delegation.sh

Changed:
<
<
This test performs a 3 delegation calls on the server (command glite-ce-delegate-proxy) with the following options:
  • --logfile
  • --conf
  • --logfile and --conf
>
>
This test performs several delegation calls on the server (command glite-ce-delegate-proxy) with any combination of --logfile and --conf options.
 

CREAM-cli-job-submit.sh

Added:
>
>
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
  • --ftp-streams this option could be ignored
Fill in the JDL section.

Prerequisites: CREAM-cli-delegation.sh

CREAM-cli-job-status-simple.sh

This test retrieves the status of an existing job (command glite-ce-job-status) with different verbosity levels (--level option)

Prerequisites: CREAM-cli-job-submit.sh

CREAM-cli-job-status-filtered.sh

This test retrieves the status of a group of existing jobs (command glite-ce-job-status) specifying:
  • --all
  • any combination of --status, --from, --to options

Prerequisites: CREAM-cli-job-submit.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-purge.sh

This test removes any data from the service about one or more jobs (command glite-ce-job-purge) specifying:
  • the ID of a submitted job
  • --all options

Prerequisites: CREAM-cli-job-submit.sh

 
Added:
>
>

CREAM-cli-job-list.sh

This test prints the list of submitted jobs (command glite-ce-job-list) with any combination of --logfile and --conf options.
 
Added:
>
>
Prerequisites: CREAM-cli-job-submit.sh
  -- AlessioGianelle - 03 Jun 2008

Revision 22008-06-03 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"
Added:
>
>

CREAM client testsuite

 A test suite for detailed testing of the command line interface to submit to a CREAM CE.
Added:
>
>
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
Line: 19 to 25
 
  • glite-ce-job-suspend
  • glite-ce-proxy-renew
Added:
>
>
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. In several cases one script requires the execution of another one first in order to prepare the environment for the test; as the test should be self-contained, the former calls the latter inside with a well defined set of options, for example CREAM-cli-job-submit.sh calls CREAM-cli-delegation.sh.

CREAM-cli-delegation.sh

This test performs a 3 delegation calls on the server (command glite-ce-delegate-proxy) with the following options:
  • --logfile
  • --conf
  • --logfile and --conf
 
Added:
>
>

CREAM-cli-job-submit.sh

 

Revision 12008-06-03 - AlessioGianelle

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="TestWokPlan"
A test suite for detailed testing of the command line interface to submit to a CREAM CE.

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

-- AlessioGianelle - 03 Jun 2008

 
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