runRi.sh is a bash script that modifies/copies various configuration files and launches the RI executable, ri (or ri.exe, depending on platform).

Because runRI.sh is a bash shell, you must either be using cygwin (for Linux/Unix emulation for Windows) or Linux.

runRI.sh changes over time. The best way to get information about current usage is to pass it -?. runRI.sh will output the various options that it can manage.

runRI.sh -?

usage: runRI.sh [-ate, -tunetest, -junit, -suite xxx, -gdb, -valgrind, -full, -capall, -restoreXAIT, -deletelog, -deletestorage, -setup, -restoreMPEENV, -coverage, -autodvr <xxx>, -tgshell -mockDLL]
 -ate runs the ri in a loop for ATE testing
 -tunetest runs the ri tune test
 -xlet <Xlet> runs the xlet as provided in the command
 -dvrtestrunner runs the ri dvrtestrunner xlet
 -junit executes unit tests
 -suite xxx, used with -junit, where xxx is the particular test suite. If ommitted all basically working test suites will be run
 -gdb runs the ri in gdb, may be combined with other flags (e.g. -tunetest or -ate)
 -valgrind runs the ri in valgrind, may be combined with other flags (e.g. -tunetest or -ate)
 -full used with -valgrind (adds -v --leak-check=full)
 -capall combined with any, captures stdout & stderr to ri-iter-N.log
 -restoreXAIT combined with any, reverts to default XAIT on each run
 -deletelog deletes RILog.txt at the start of this script
 -deletestorage deletes C:/QARepo/riExOCAPRI/trunk/ri/RI_Stack/bin/CableLabs/simulator/Win32/debug/env/persistent and C:/QARepo/riExOCAPRI/trunk/ri/RI_Stack/bin/CableLabs/simulator/Win32/debug/env/storage
 -setup sets up config files before running the ri, may be combined with other flags (e.g. -tunetest or -ate)
 -restoreMPEENV restores the mpeenv.ini file on exit.
 -coverage instruments the stack for test coverage, dumps the data on restart, EMMA is required to be installed
 -autodvr xxx, uses DvrExercisor, where xxx is the (optional) command file (e.g. random_tune.cmd)
 -restart auto-restarts the executable in case of death
 -tgshell runs the ri with tgshell (requires TGSHELL_HOME be set and point to the unzipped tgshell xlet)
 -mockDLL combined with any, enables the use of the mock.dll for DTCP/IP
 RILog.txt and ri-iter-X.log are both written to the path $PLATFORMROOT/$RILOGPATH - to change where log files are written, assign the $RILOGPATH environment variable to a relative path
Note: Basically working test suites are DeviceExtSuite DiagnosticsSuite EASTestSuite FPSuite HaviSuite ImplSuite JavaTVSuite JavaxSuite ManagerSuite MediaSuite MiscSuite SNMPSuite DVRSuite OrgSuite
test suites that hang or crash the RI are DiagnosticsSuite ImplSuite MediaSuite OrgSuite

Notes:

  • Generally want/need to include -setup, unless you are modifying configuration files yourself.
  • junit results are output into junit_test_results.log
  • No labels