A list of existing tests as of June 2006. This list is no longer being updated.

edg-tests (Gilbert testsuite)

Release TSTG 1.0.1 available since 03/22/06. It introduces few new features, but merges all fixes and tunings since Dec 2004. Tars available here

WMS

Provided by Mario Reale, currently used by Di. A sample output is here. The test can be run within the edg-tests framework. A special grid flavour field has been introduced to distinguish between "edg" and "glite" commands. These changes are not in TSTG 1.0.1. The following tests are available:

1. DNS Check that a reverse DNS lookup works for all of the supplied host names. The host names must be fully qualified. The reverse DNS lookup is done as a basic part of checking the validity of host certificates. If the lookup does not work, then secured requests to that machine will fail (e.g. job submission, GridFTP transfers, etc.).
2. User Script This Storm is a JobStorm where the user can provide either the JDL file or the Script to send and run on the Wns. Run providing a basic script to be executed on the WN.
3. User JDL This Storm is a JobStorm where the user can provide either the JDL file or the Script to send and run on the Wns. Run providing a simple JDL file.
4. CE gatekeeper Checks that a globus-job-run, a globus-job-submit, and a globusrun with two-phase commit all work. The two-phase commit test is extremely important as edg-job-submit commands will fail unless this works correctly. Checks that a globus gatekeeper is minimally functioning. For the two-phase test to be useful, it should be run from a machine outside of the gatekeeper's local firewall.
5. CE Cycle Checks one by one that the site specific CEs are indeed operational. Taking into account the CEs specified in the site.conf, the test is meant to check (through a glite-job-list-match operation) that these CEs are indeed accepted by the WMS. Then a job is sent to each CE in turn, to check they are fully alive and operational. This will replace the simple HelloWorld test, where the CE itself was not specified. The summary page displays the results of the former check within the MATCHING step, and the latter check within the RUNNING step.
6. Input Output It is a basic test based on the User JDL one which checks the proper execution and output retrieval of a set of jobs using Input and Output sandBoxes.
7. RB val/Pile Storm This PileStorm derives from the standard JobStorm in a simple way: a stack of JDL files together with their relevant Script files is previously created, while the file names are recorded on a service file. This allows to mix in a single storm several kinds of tests, in order to submit the jobs in parallel (time savings). Then the PileStorm itself is launched and brokers the jobs on both stacks. This rather special storm is currently only used to for Unit testing of the WMS and CEs, and the simple jobs which are executed all return an '[OK]' string in their output.
8. CalStorm R3 This submits a job which simply sleeps for the given period of time. If no time is given, the delay defaults to 5 minutes. The syntax of the time is that for the unix sleep command. E.g. 30s, 5m, and 2h are 30 seconds, 5 minutes, and 2 hours, respectively. It is run with RetryCount = 3.
9. CalStorm R0 This submits a job which simply sleeps for the given period of time. If no time is given, the delay defaults to 5 minutes. The syntax of the time is that for the unix sleep command e.g. 30s, 5m, and 2h are 30 seconds, 5 minutes, and 2 hours, respectively. It is run with RetryCount = 0.
10. JS Sleep This submits a simple job which simply echoes the [OK] string. It does this from multiple jobs running on WNs, i.e. a job "storm".
11. DAG Tests the proper submission and execution of a very basic DAG job , checking status and output retrieval.
12. WMS NS Job submission stress test It's a parallel thread of submission stress test of the WMS and the Network Server on the WMS node.
13. WMS NS Job Submission stress test catalog It writes a file on the FireMan catalog from a job running on the Worker Node.

WMS bulk submission

Work being done Hui-Min LIN and Di. A description is here.

VOMS

Information provided by Maria Alandes Pradillo.

Find a more detailed description of VOMS tests here.

R-GMA

Provided by Laurence Field on TestingRGMA

R-GMA developers provide some tests scripts which can be found in org.glite.testsuites.rgma. An R-GMA functional tests document is also available.

DPM and LFC

Tests are bundled with the LCG-DM module in CVS and have been written by Gilbert. Here is a description on how to use them:

Pour utiliser la globalSuite: A) Construire l'environnement - Faire un cvs checkout de LCG-DM - Aller dans le dir LCG-DM - Faire un make complet - Descendre dans LCG-DM/socket - Faire un make - Aller dans LCG-DM/test - Faire un make B) Tourner la suite (depuis lxb2057) - Aller dans LCG-DM/test/dpm - creer la variable

>> setenv GSI_PASSWORD your-pwd

- creer le dir /var/tmp/your-login - lancer la suite par la commande :

>> globalSuite the-short-node-name &

- l'output sort directement dans un fichier du type: /var/tmp/grodid/global/lxb1737/2006-03-20/fil184401/logFile - les resultats globaux sont sortis a la console.

Si tt est correct, tu dois avoir: OVERALL Score: OK=30 FAILED=0

FTS

Provided by Gergely Debrezceni and Radoslava (Radi) Goranova. See also TestingFTS

LB

Othmane Bouhali and Shkelzen Rugovac (Université Libre de Bruxelles) work on that.

hydra

Stores keys for data encryption. Some tests available in CVS module org.glite.data.hydra-cli/test. Developed by Akos Frohner.

amga

Generic metadata catalog. Testsuite in CVS module org.glite.amga.server/test tests cli clients, server functionality and DB compatability. Amga developers plan to enhance it. For the Python api there is a test in CVS module org.glite.amga.api-python/test. Contacts: Birger Koblitz, Viktor Pose.

gfal

Krzysztof Nienartowicz has some tests.

-- AndreasUnterkircher - 08 Dec 2006