The run_test script is automatically generated as Common Test is installed (please see the Installation chapter in the Common Test User's Guide for more information). The script accepts a number of different start flags. Some flags trigger run_test to start the Common Test application and pass on data to it. Some flags start an Erlang node prepared for running Common Test in a particular mode.
run_test also accepts Erlang emulator flags. These are used when run_test calls erl to start the Erlang node (making it possible to e.g. add directories to the code server path, change the cookie on the node, start additional applications, etc).
If run_test is called without parameters, it prints all valid start flags to stdout.
run_test [-dir TestDir1 TestDir2 .. TestDirN] | [-suite Suite1 Suite2 .. SuiteN [-case Case1 Case2 .. CaseN]] [-step] [-config ConfigFile1 ConfigFile2 .. ConfigFileN] [-logdir LogDir] [-silent_connections [ConnType1 ConnType2 .. ConnTypeN]] [-stylesheet CSSFile] [-cover CoverCfgFile] [-event_handler EvHandler1 EvHandler2 .. EvHandlerN] [-repeat N [-force_stop]] | [-duration HHMMSS [-force_stop]] | [-until [YYMoMoDD]HHMMSS [-force_stop]]
run_test -spec TestSpec1 TestSpec2 .. TestSpecN [-config ConfigFile1 ConfigFile2 .. ConfigFileN] [-logdir LogDir] [-allow_user_terms] [-silent_connections [ConnType1 ConnType2 .. ConnTypeN]] [-stylesheet CSSFile] [-cover CoverCfgFile] [-event_handler EvHandler1 EvHandler2 .. EvHandlerN] [-repeat N [-force_stop]] | [-duration HHMMSS [-force_stop]] | [-until [YYMoMoDD]HHMMSS [-force_stop]]
run_test -vts [-browser Browser] [-config ConfigFile1 ConfigFile2 .. ConfigFileN] [-dir TestDir1 TestDir2 .. TestDirN] | [-suite Suite [-case Case]]
run_test -refresh_logs [-logdir LogDir]
run_test -shell [-config ConfigFile1 ConfigFile2 ... ConfigFileN]
run_test -ctname NodeName
run_test -ctmaster
Please read the Running Test Suites chapter in the Common Test User's Guide for information about the meaning of the different start flags.