I am trying to integrate and iTest test case as a script executed from Gale Technologies' LabManager tool. The integration requires the iTest test case to be executed by using itestcli as a cgi script for Apache web server, using the command below.
"C:/Program Files/Fanfare/iTest 3.2/itestcli.bat" -w "C:/Fanfare/Workspace" -l "itest_log.txt" -r itest_report.fftr -summary "project://Spirent_project/Spirent_project/test_cases/stal.fftc"
As expected, I get std output on the command line, if I execute the above from the command line or as a .bat file. However if I run it as a cgi script as is required by LabManager, I don’t get any standard output back into LabManager's console where I normally see any runtime output. Runtime info is logged in the log file specified by the -l switch -- which is evidence that the test case does get executed and itestcli has _at least_ some level of control over standard out. However, it appears that standard output is redirected somewhere when itestcli executes as a batch script.
Has anyone run into this issue?
I will appreciate any insight into how itestcli handles standard and error output in principle and in this specific case as a cgi script.
Thanks,
Milen