The datacondAPI's MDC Tests

Test objectives

Setup

The resource file  .datacondAPI.rc  needs to be installed in home directory of the tester. Edit this file to have the correct username, password, email and host specified. All these variable are located near the begining of the file. No other values should require modification.

The script  mymaster.tcl  needs to go into the directory of MDC scripts. It can be found in CVS in ldas/api/datacondAPI/tcl/test.

The script  verifymdc.tcl   needs to go into the directory of MDC scripts. It can be found in CVS in ldas/api/datacondAPI/tcl/test. It is used to verify that all emails for the MDC tests have been received and that the success and exception emails match the expected numbers.

The directory containing the datacond MDC response files should be mounted under /ldas_outgoing/jobs/mdc.

Test Execution

Change to the directory containing mymaster.tcl. . Both standard in and standard out should be redirected to a file for future analysis. The site defaults to dev.

Analysis

Once the script has completed, there should be a total of 163 email from the ldas user with the subject line begining with "NORMAL". Verify that each job listed completed correctly (either generating exceptions or generating results) without aborting.

The general rule is, the jobs that are numbered 01[abcde] should throw exceptions, and the ones numbered 02[abcde] should generate results. There are some exceptions, though.  The REALIMAGABSAPI01A* jobs and RESAMPLEAPI01C* jobs should generate results . Also all the PIPE01 jobs generate results.

To verify the above, Have your MDC emails filtered into one sub-directory.


cd < email sub-directory >
<your cvs toplevel>ldas/api/datacondAPI/tcl/test/verifymdc.tcl \ 
<your cvs toplevel>/ldas/api/datacondAPI/tcl/test/results/mymaster.log 
> & verify.log & &
Expected 137 results and 282 errors out of 419 emails.

Possible errors at datacondAPI are: bad alloc and the individual tests should re-run again when that happens.