WMS Test Plan
Service Description
Features/Scenarios to be tested
'JOB SUBMISSION' (implemented)
Registers the job into the wmproxy, delivers it to the WM that submits it to the grid.
Normal workflow - correct input
'Job submission' is to be tested with the following different types of jobs as input:
- Normal
- DAG
- Perusal
- MPICH
- Collections
Pass/Fail Criteria
Error workflow - erroneous input
- provide a jdl with a missing mandatory attribute
Pass/Fail Criteria
'JOB LISTMATCH' (implemented)
Delivers the job to the WM that selects the best matching resources for the job on the GRID.
Normal workflow - correct input
Job listmatch is to be tested with 'Normal' type of jobs
Pass/Fail Criteria
Error workflow - erroneous input
- provide a .jdl with a 'Requirements' attribute that will not be satidfied for sure, like for ex.
Requirements = false ;
Pass/Fail Criteria
When no resources are found and a message such as the following is returned:
==================== glite-wms-job-list-match failure ====================
No Computing Element matching your job requirements has been found!
==========================================================================
'JOB OUTPUT' (implemented)
- Submits a job
- waits for it to be finished
- retrieves the output and purges relative sandboxes.
Normal workflow - correct input
This feature is to be tested both for 'normal' and 'collection' type of jobs.
Pass/Fail Criteria
Error workflow - erroneous input
- trying to retrieve the output of a job for which it has already been retrieved
Pass/Fail Criteria
Error workflow - erroneous input
- trying to retrieve the output of a job that is not in the right status 'Done'
Pass/Fail Criteria
- Pass -> a message as the following is returned
Error - Output not yet Ready
Current Job Status is: Scheduled
'JOB CANCEL' (implemented)
- Submits a job
- retrieves the jobid of the submitted job
- forwards the cancel request to the WM and logs it into the LB.
Normal workflow - correct input
The feature is to be tested for 'Normal' type of jobs.
Pass/Fail Criteria
Error workflow - erroneous input
- trying to cancel a job that was already cancelled
Pass/Fail Criteria
'JOB STATUS' (implemented)
- Submits a job
- retrieves the jobid of the submitted job
- waits a few seconds and check the job status.
Pass/Fail Criteria
Error workflow - erroneous input
- trying to get the status of a job that was submitted by another user
- Pass -> status is not returned and a message such as the following is returned instead
**** Error: API_NATIVE_ERROR ****
Error while calling the "Status:getStatus" native api
Unable to retrieve the status for: https://egee-rb-01.mi.infn.it:9000/EJ8u22zlRLl5uBj7GJA0CQ
edg_wll_JobStatus: Operation not permitted: matching jobs found but authorization failed
Tests required that are not yet implemented
- In general all the tests described above need to be enhanced, so that also the final status of the job is checked and it is what it was expected to be, In particular some of the following possible scenarios should be tested:
- submission of a job type 'Collection' checking for coherence among the final status of all the nodes and of the parent node
- submission of a job type 'normal' with different type of input checking for the final status and the job output
- submission of a job type 'DAG' checking for the final status
- Regression tests on already known bugs can be created using the info stored here http://glite.cvs.cern.ch/cgi-bin/glite.cgi/org.glite.testsuites.ctb/WMS/regression/
--
ElisabettMolinari - 27 Jan 2009