OLAS

vcsolac : automatic environment

* Commandline options (no parameter, polldir, forcetransfer, logdb, ...)

* Random test (FITS file >35 MB, >64 MB, >128 MB, )

* Environment settings (RCPW_CONFIG, OLAS_ID, DHS_CONFIG)

* File naming ( starting vcsolac with 1 file in queue)

* File format (data file contains valid fits file)

* Full disk behaviour

* Error Handling (corrupted image but valid FITS header, corrupted FITS header, no FITS format, r/w protection on FITS files, rcp failed during transmission of bulk-msg, SIGTERM handling,

* Stress Test (2500 bulk messages in the VCSOLAC queue)

* Miscellaneous (MJD-OBS missing, MJD-OBS=zero, ...)

dhs : automatic environment

* Commandline options (no parameter, verbose levels, logpath, polldir, baddir, logdb, ...)

Random test (VCSOLAC-sim sends a fits file but the fits file contains already the keywords; fits file contains wrong CHECKSUM; ...)

* Environment setting (cleanup-dhs)

* File naming

* Message format *.bulk (bulk message contains parts of the fits header; part of image data; only image data; ...)

* Message format *.plain (invalid password; wrong subscriber/supplier name; only password+priority given; ...)

* Naming convention FITS file (MJD-OBS not available, PRO.TYPE not available, PIPEFILE not available; ...)

* Naming convention Message file

* Error Handling ( corrupted image but valid FITS header, simulate reboot, r/w protection on FITS files

* Stress Test (Start dhs when 1000 bulk messages in the DHS queue; 100 vcsolac tries to connect)

* Miscellaneous (bulk-msg is sent, but no ctrl- and plain-msg; Running dhs twice at same host;

dhsSubscribe : automatic environment

* Commandline options (no parameter, dhsdata, polldir, logpath, backlog, backto, rename, filetype, where, logdb, ...)

* Naming convention Message file (name of bulk message is not MJD like, <filename> of bulk message is MJD like but MJD-OBS is not the same like in fitsheader)

* Error Handling (1st send of bulk-msg fails; 1st send of bulk-msg is valid, but 2nd try fails; ...)

* Miscellaneous (dhsdata and polldir at different partitions

frameIngest : automatic environment

* Commandline options (Misspelling keyword)

* Environment setting (INS_ROOT not defined, SYBASE with wrong value)

* ASM ingestion (valid ASM, asmdim file with errors, ...)

* Database handling (open a connection, write a connection, close a connection)

DPPACKER : automatic environment

* Commandline options (no option given; -size; -starttime=<YYYY-MM-DD>; -endtime YYYY-MM-DD; ...)

* Miscellaneous (Starting dppacker again with -incremtental 1;

OLAS : automatic environment

* dhs <--> vcsolac (Cleanup-dhs while dhs is transmitting bulk-msg; rcp fails, while dhs is transmitting bulk-msg; ...)After vcsolac is started, several instruments-files are sent; cleanup-vcsolac is sent during transmission; Running vcsolac and dhs at same host;

* dhs <--> frameIngest ( A fits file is sent to vcsolac, which does not contain any ESO parameters; tc files are sent to vcsolac; Testing watchdog frameIngest; dhs and frameIngest using same environment; ...)

* dhs <--> dhsSubscribe (dhs will be closed while executing the bulk-message)

* dhs <--> dhs (dhs2 connects as subscriber to dhs1; backlog handling, ...)

* The whole chain (Sending arrived fits file to different subscribers; Sending real ASM files; Running 2 frameIngest to the same database but on different machines;

* Dictionary test (Check, if all parameters in DFS-OLASTest-instruments*.fits are defined in delivered dictionary; Handling dictionary;

* Test with simulator (sending paf- and fits-files in real time)

* Miscellaneous (Changing parameter MJD-OBS;