Development of test suites for the certification of EGEE-II Grid middleware Task 2: The development of testing procedures focused on special details of various software features PNPI – Yu. Ryabov, N. Klopov CERN-INTAS meeting, 26 July 2007, Dubna

Development of test suites for the certification of EGEE-II Grid middleware Set of WMS tests were developed according to the request from gLite certification team: 1.Parametric job test 2.Interactive job test 3.Checkpointable job test 4.Partitionable job test 5.Long and complex JDL stress test Some of the tests were included into certification SAM framework. 5 bugs were submitted in Savannah.

Parametric job test The developed test script does the following: -Generation of JDL file using the input parameters -Submission of parametric job -Monitoring the status of the nodes(sub-jobs) -Retrieval output files for each nodes -Checking of the following: 1.the number of the submitted nodes is correct 2.the names of the submitted nodes are correct 3.the proper arguments were created for the each of nodes 4.the proper named output files were retrieved from nodes 5.the proper named files were transfered for the each of the nodes The test can be used in stress mode ( large number of nodes)‏

Interactive job test The test script does the following: -Generation of JDL file for interactive job -Submission of the job -Launch the subprocesses which will communicate with the pipes -Job status monitoring -Communication with the running job: -- Interchange with the job with the asynchronous "Welcome" messages -- Send the message to the job -- Read the response - - Repeat the two latter steps for the given number of times -Retrieval job output files and checking of the job report -Remove pipes and shadow processes

Checkpointable job test The test script does the following: - Generation of the JDL file for Checkpointable job using input parameters - Submission of the job (glite-wms-job-* or glite-job-* command)‏ The job try to compile C++ program which has to do the following: - get the CurrentStep - cycle from current step to last step (getNextStep) saving state as = - if make command fail then run C++ job from InputSandbox - Job status monitoring until job will get status Done/Abort/Canceled - Retrieval Checkpoint States saved by job using the command glite-wms-job-get-chkpt - Checking of the correctness of the Job Checkpoint States - Retrieval job output files and print the job report

Partitionable job test The test script does the following: 1.Generation of the JDL file for partitionable job using input parameters 2.Submission of the partitionable job 3.Status monitoring 4.Retrieval output files for each of the node. 5.Checking of the following: -All states were distributed between nodes -There are no additional states (checkpoints)‏ -Check that all subjobs IDs were set for postjob as checkpoint states

Large JDL stress test The main goal of this stress test is to check the possibility of WMS to handle the job with the very large JDL file. There are 3 JDL attributes which were used for the JDL expansion – Environment, InputSanbox and OutputSanbox. The size of the JDL can be defined using the following script option: -Environment -v : -InputSandbox -i : : -OutputSandbox -i : :

Testbed The testbed was installed which provide the following gLite 3.0 services: CE WMS+LBBDIISE(DPM)‏ LFCUIWN