Fix Version/s: None
Sprint:TSSW Sprint - Sep 28 - Oct 12, TSSW Sprint - Oct 12 - Oct 26
Team:Telescope and Site
Write the test framework of SAL LabVIEW API. This task begins to construct a framework to test the LabVIEW API for each new SAL update. In the past, we used the component CSC in LabVIEW to test this. Now, we need a framework to test this automatically. The SAL LabVIEW APIs rely on the shared memory, which is not needed for the C++ and JAVA APIs. Therefore, this kind of automatic test framework should be helpful for the maintenance of CSC in LabVIEW. This task is in the phase 3.
Based on Dave, I should use the LSST_TEST_LVDEBUG instead of LSST_Test_LVDEBUG to get the debug message. The CSC name should be capitalized in environment variables.
Added the command line task to get the SAL event (use the CPP executable to send the SAL event). At this moment, only the summary state event is supported. Added the test cases.
The output of monitor is outputMonitor.txt.
The output of test of getting the event is reportGetEvent.txt.
Please help to review the PR:
To use the command line task of getting the event (only the summary state at this moment), do:
labview64 $path_to_test_vi -- $abs_path_to_monitor_file $abs_path_to_lvlib $abs_path_to_cpp_send_summary_state
For example, in my case:
labview64 src/testGetEventTask.vi -- /home/ttsai/Documents/github/ts_SALLabVIEW_test/tests/testData/SALLV_Test_Monitor /home/ttsai/Documents/github/ts_SALLabVIEW_test/tests/testData/SALLV_Test.lvlib /home/ttsai/Documents/github/ts_sal/test/Test/cpp/src/sacpp_Test_summaryState_send
The report will be in the log/ directory. The related settings are in config/ directory. The details can follow the README.md.
Tested to publish 500 times of summary state event by CPP and get them by LabVIEW. There is no problem to receive all messages.
Get the event by the file path only (do not instantiate any SAL LabVIEW vi):