User's Guide
Reference Manual
Release Notes
PDF
Top

Common Test
Reference Manual
Version 1.5.5

Expand All
Contract All

Table of Contents

# ct_run

### COMMAND

ct_run

### COMMAND SUMMARY

Program used for starting Common Test from the OS command line.

### DESCRIPTION

The ct_run program is automatically installed with Erlang/OTP and Common Test (please see the Installation chapter in the Common Test User's Guide for more information). The program accepts a number of different start flags. Some flags trigger ct_run 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.

There is an interface function that corresponds to this program, called ct:run_test/1, for starting Common Test from the Erlang shell (or an Erlang program). Please see the ct man page for details.

ct_run also accepts Erlang emulator flags. These are used when ct_run 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).

With the optional flag:

    -erl_args

it's possible to divide the options on the ct_run command line into two groups, one that Common Test should process (those preceding -erl_args), and one it should completely ignore and pass on directly to the emulator (those following -erl_args). Options preceding -erl_args that Common Test doesn't recognize, also get passed on to the emulator untouched. By means of -erl_args the user may specify flags with the same name, but with different destinations, on the ct_run command line.

If -pa or -pz flags are specified in the Common Test group of options (preceding -erl_args), relative directories will be converted to absolute and re-inserted into the code path by Common Test (to avoid problems loading user modules when Common Test changes working directory during test runs). Common Test will however ignore -pa and -pz flags following -erl_args on the command line. These directories are added to the code path normally (i.e. on specified form)

If ct_run is called with option:

    -help

it prints all valid start flags to stdout.

### Run tests from command line

    	ct_run [-dir TestDir1 TestDir2 .. TestDirN] |
    	[[-dir TestDir] -suite Suite1 Suite2 .. SuiteN
    	 [[-group Group1 Group2 .. GroupN] [-case Case1 Case2 .. CaseN]]]
    	[-step [config | keep_inactive]]
    	[-config ConfigFile1 ConfigFile2 .. ConfigFileN]
    	[-userconfig CallbackModule1 ConfigString1 and CallbackModule2
    	 ConfigString2 and .. and CallbackModuleN ConfigStringN]
    	[-decrypt_key Key] | [-decrypt_file KeyFile]
    	[-label Label]
    	[-logdir LogDir]
    	[-logopts LogOpts]
    	[-silent_connections [ConnType1 ConnType2 .. ConnTypeN]]
    	[-stylesheet CSSFile]
    	[-cover CoverCfgFile]
    	[-event_handler EvHandler1 EvHandler2 .. EvHandlerN] |
            [-event_handler_init EvHandler1 InitArg1 and
    	 EvHandler2 InitArg2 and .. EvHandlerN InitArgN]
    	[-include InclDir1 InclDir2 .. InclDirN]
    	[-no_auto_compile]
    	[-muliply_timetraps Multiplier]
    	[-scale_timetraps]
            [-repeat N [-force_stop]] |
            [-duration HHMMSS [-force_stop]] |
            [-until [YYMoMoDD]HHMMSS [-force_stop]]
    	[-basic_html]

### Run tests using test specification

    	ct_run -spec TestSpec1 TestSpec2 .. TestSpecN
    	[-config ConfigFile1 ConfigFile2 .. ConfigFileN]
    	[-userconfig CallbackModule1 ConfigString1 and CallbackModule2
             ConfigString2 and .. and CallbackModuleN ConfigStringN]
    	[-decrypt_key Key] | [-decrypt_file KeyFile]
    	[-label Label]
    	[-logdir LogDir]
    	[-logopts LogOpts]
    	[-allow_user_terms]
    	[-silent_connections [ConnType1 ConnType2 .. ConnTypeN]]
    	[-stylesheet CSSFile]
    	[-cover CoverCfgFile]
    	[-event_handler EvHandler1 EvHandler2 .. EvHandlerN] |
            [-event_handler_init EvHandler1 InitArg1 and
    	 EvHandler2 InitArg2 and .. EvHandlerN InitArgN]
    	[-include InclDir1 InclDir2 .. InclDirN]
    	[-no_auto_compile]
    	[-muliply_timetraps Multiplier]
    	[-scale_timetraps]
            [-repeat N [-force_stop]] |
            [-duration HHMMSS [-force_stop]] |
            [-until [YYMoMoDD]HHMMSS [-force_stop]]
    	[-basic_html]

### Run tests in web based GUI

            ct_run -vts [-browser Browser]
            [-dir TestDir1 TestDir2 .. TestDirN] |
            [[dir TestDir] -suite Suite [[-group Group] [-case Case]]]
    	[-config ConfigFile1 ConfigFile2 .. ConfigFileN]
    	[-userconfig CallbackModule1 ConfigString1 and CallbackModule2
             ConfigString2 and .. and CallbackModuleN ConfigStringN]
    	[-logopts LogOpts]
    	[-decrypt_key Key] | [-decrypt_file KeyFile]
    	[-include InclDir1 InclDir2 .. InclDirN]
    	[-no_auto_compile]
    	[-muliply_timetraps Multiplier]
    	[-scale_timetraps]
    	[-basic_html]

### Refresh the HTML index files

    	ct_run -refresh_logs [-logdir LogDir] [-basic_html]

### Run CT in interactive mode

    	ct_run -shell
    	[-config ConfigFile1 ConfigFile2 ... ConfigFileN]
    	[-userconfig CallbackModule1 ConfigString1 and CallbackModule2
             ConfigString2 and .. and CallbackModuleN ConfigStringN]
    	[-decrypt_key Key] | [-decrypt_file KeyFile]

### Start a Common Test Master node

    	ct_run -ctmaster

### See also

Please read the Running Test Suites chapter in the Common Test User's Guide for information about the meaning of the different start flags.