When running a testcase from HPQC, iTestCLI is called. Sometime, there are errors and you see a cmd window popup very briefly, and then shuts down almost immediately, the testcase cannot run, test result is failed. So, you should figure out how it is. There are some tips as bellow can help
The tip to show the cmd window when iTestCLI is called.:
1. Goto iTest folder, default is C:\Program Files\Spirent Communications\iTest 4.2
2. Edit itestcli.bat file as below:
- Modify @echo off to @echo on
- Insert Pause at the bottom
- Save file
- Run the testcase from HPQC again
See the picture:
3. Now, you can see all behaviors when iTestCLI is running as the picture:
4. Restore itestcli.bat when the error is fixed.
The full command when HPQC call iTestCli:
java -classpath "C:\Program Files\Spirent Communications\iTest 4.2\itestcli.jar;C:\Program Files\Spirent Communications\iTest 4.2\commons-cli-1.1.jar;C:\Program Files\Spirent Communications\iTest 4.2\xmlwriter-2.2.jar" com.fnfr.svt.cli.ITestCli -i 5 -w "D:\Sang\HSN\runtime-iTest" -qc -qcu "sang.ngo" -qcp "123456" -qcs "http://220.127.116.11:8080/qcbin/wcomsrv.dll" -qcpr "ITEST" -qcd "SPIRENT" -qct "Root\Sample\Sample\Sample" "C:\Users\sang.ngo\AppData\Local\Temp\TD_80\116\6f91179f\Test\5\5\5\Forum.fftc"
All arguments on is used when HPQC call iTestCLI:
-I,-w, -qc, -qcu, -qcp, -qcs, -qcpr, -qcd, -qct
To know what these arguments are, please type the command to cmd window: itestcli ? or search topic “itestcli command reference” on Help in iTest
To execute iTest testcase from HPQC, some enviroment variables should be set correctly. If you haven't set them yet, please search topic “Executing Spirent iTest test cases on remote hosts” on Help in iTest for more details.
Be sure that you have the installation directory for iTest listed in the PATH environment variable. Also, be aware that spaces after the semicolon cause Microsoft to ignore the rest of the definition, so remove any spaces after the semicolon that separates the PATH entries.