Test jig for acontrol-cmdClient interface

transientskp / aartfaac-control

AARTFAAC control scripts

0 stars 0 forks source link

Test jig for acontrol-cmdClient interface #3

Closed hsuyeep closed 9 years ago

hsuyeep commented 9 years ago

cmdClient will be a 'forever' running process on multiple machines. As such, it needs to generate sensible status output for any input.
We should be able to test cmdClient + acontrol in an offline mode, be able to run the client on local nodes to mimmic actual hardware, and be able to run servers/pipelines on offline test data.
Test jig should send multiple queries over a reasonable lifetime and start/stop multiple sessions of the slave programs.

hsuyeep commented 9 years ago

Include a dummy LOFAR parset, so we can fire off acontrol at any time for tests.

hsuyeep commented 9 years ago

Folkert created the aartfaac-control/emulator/emulate.py script to generate a dummy parset in the aartfaac-control/data area. The parset has a trigger time some 10s of secs after running the emulate script, and a duration of 1 minute. Tested and found adequate for testing cmdclient interface.