Difference: WMSWorkPlan (5 vs. 6)

Revision 62011-03-03 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestPage"
Line: 52 to 52
 

Testsuite description

Changed:
<
<

WMS-command_job-delegate-proxy.sh

>
>

WMS command tests

WMS-command_job-delegate-proxy.sh

  This test is intended to verify glite-wms-job-delegate-proxy command
Line: 69 to 71
 
  • Try to delegate with an expired proxy
  • Try to submit with an expired delegation
Added:
>
>

WMS-command_job-list-match.sh

 
Added:
>
>
This test is intended to verify glite-wms-job-list-match command
 
Added:
>
>
Test the command with these options:
  • --logfile
  • --output
  • --endpoint
  • --rank
success if command returns 0
 
Added:
>
>
  • Test a failure matching (requirements = false). Success if no matching is found.
  • Test a restricted matching (only Cream CEs). Success if none LCG CE matches.
  • Test delegation proxy option --delegationid (delegate before the mm). Success if command returns 0.
 
Added:
>
>

WMS-command_job-info.sh

 
Added:
>
>
This test is intended to verify glite-wms-job-info command
 
Changed:
<
<

Releases and Changelog

>
>
Test these options for all the command: --jdl-original --jdl --proxy --delegationid
  • --version
  • --input
  • --config
  • --output
  • --logfile
  • --endpoint
  • all options toghether
success if command returns 0

  • Check if the JobID is set correctly in the retrieved jdl
  • Check if the expiration time of the delegation is set correctly"

WMS-command_job-submit.sh

This test is intended to verify glite-wms-job-submit command

Test the command with these options:

  • --version option
  • --endpoint option
  • --output option
  • --logfile option
  • --nomsg option
  • all options together
success if command returns 0

  • --input option (with --noint)
  • --resource option
success if job is submit to the required CE

  • --register-only option
success if job is in state Submitted

  • --start option
success if job correctly terminated

  • --transfer-files --proto option
success if job output is as expected (i.e. files are correctly transferred)

  • --valid option
  • --to option
success if ExpiryTime is correctly set in the jdl and if job aborted with reason request expired

  • --default-jdl option
success if the attribute id the default-jdl is add to the job's jdl

WMS-command_job-status.sh

This test is intended to verify glite-wms-job-status command

Test the command with these options:

  • --version
  • --config
  • --output
  • --logfile
  • --input
success if command returns 0

Testing these options requires certain indexing capabilities to be enabled on the LB server, so they can failed.

  • --exclude (exclude Waiting, Done, Cleared and Aborted jobs)
  • --status (look for Waiting job)
  • --user-tag
success if command output is as expected.
 
Added:
>
>

WMS-command_job-logging-info.sh

 
Added:
>
>
This test is intended to verify glite-wms-job-logging-info command
 
Added:
>
>
Test the command with these options:
  • --version option
  • --config
  • --output
  • --logfile
  • --input
  • --to
  • --from
  • --event (show only ACCEPTED events)
  • --exclude (exclude ACCEPTED events)
  • all the options together (extract only EnQueued events)
success if command returns 0 and output is as expected.

WMS-command_job-output.sh

This test is intended to verify glite-wms-job-output command

Test the command with these options:

  • --version
  • --logfile
  • --dir
  • --nosubdir
  • --list-only
  • --nopurge
  • --input
success means that the status is "CLEARED" (otherwise a WARNING is produced) and that output files std.out and std.err are correctly retrieved.

  • Try to retrieve output of a Cleared job. Success if command failed.

WMS-command_job-cancel.sh

This test is intended to verify glite-wms-job-cancel command

Test the command with these options:

  • --version
  • --config
  • --output
  • --logfile
  • --input
  • all options together
success means that the final state of the job is "Cancelled"

  • cancel a finished job. Succes if command fails.

WMS-command_job-perusal.sh

This test is intended to verify glite-wms-job-perusal command

Test the command with these options:

  • --version
  • --set
  • --get
  • --get with --dir
  • --get with --nodisplay and --all
success if the retrieved pieces of file are exactly the job's output.
 
Added:
>
>

Functionality tests

 
Added:
>
>

WMS-job-cycle.sh

 
Added:
>
>
Test a complete job cycle: from submission to get-output
  • submission of a normal job to an LCG-CE
  • submission of a normal job to a CREAM CE
success if job terminated correctly and the retrieved output files are the two expected files (std.out and std.err)

You can try submission to a specific CE using command's option -c

WMS-job-resubmit.sh

Test the two types of possible resubmissions.

  • shallow resubmission
  • deep resubmission
Success if job fails with the expected reason
 

Regression tests

Location: http://glite.cvs.cern.ch/cgi-bin/glite.cgi/org.glite.testsuites.ctb/WMS/regression/

Deleted:
<
<
To create a regression test please follow this simple rules:
 
Deleted:
<
<
  • Create a description file: <bug number>.txt with this information:
Bug: <put the bug number>
Link: <link to savannah bug page>
Summary: <short description of the bug>
And then a list of actions that should be taken to test the bug.

  • If need create a jdl file: <bug number>.jdl
 
Changed:
<
<
You can add also this attribute to jdl that could be useful for future checks:
>
>

Releases and Changelog

 
Deleted:
<
<
usertags = [ bug = "<put bug number>" ];
 
Deleted:
<
<
  • If need create a bash script file: <bug_number>_exe.sh
 
Deleted:
<
<
You can found also a directory with some example file of data to use as InputSandBox and a directory with not silly executables.
 
Deleted:
<
<
These tests are NOT supposed to be run automatically so some manual intervention should be required also on the WMS machine.
 

-- AlessioGianelle - 08 Jul 2008

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback