User's Guide
Reference Manual
Release Notes
PDF
Top

Common Test
Reference Manual
Version 1.5.3

Expand All
Contract All

Table of Contents

- common_test
  - Top of manual page
  - Module:all/0
  - Module:groups/0
  - Module:suite/0
  - Module:init_per_suite/1
  - Module:end_per_suite/1
  - Module:init_per_group/2
  - Module:end_per_group/2
  - Module:init_per_testcase/2
  - Module:end_per_testcase/2
  - Module:Testcase/0
  - Module:Testcase/1
- ct_run
- ct
  - Top of manual page
  - abort_current_testcase/1
  - add_config/2
  - comment/1
  - decrypt_config_file/2
  - decrypt_config_file/3
  - encrypt_config_file/2
  - encrypt_config_file/3
  - fail/1
  - get_config/1
  - get_config/2
  - get_config/3
  - get_status/0
  - get_target_name/1
  - install/1
  - listenv/1
  - log/1
  - log/2
  - log/3
  - pal/1
  - pal/2
  - pal/3
  - parse_table/1
  - print/1
  - print/2
  - print/3
  - reload_config/1
  - remove_config/2
  - require/1
  - require/2
  - run/1
  - run/2
  - run/3
  - run_test/1
  - run_testspec/1
  - sleep/1
  - start_interactive/0
  - step/3
  - step/4
  - stop_interactive/0
  - testcases/2
  - timetrap/1
  - userdata/2
  - userdata/3
- ct_master
  - Top of manual page
  - abort/0
  - abort/1
  - progress/0
  - run/1
  - run/3
  - run/4
  - run_on_node/2
  - run_on_node/3
  - run_test/2
- ct_cover
  - Top of manual page
  - add_nodes/1
  - remove_nodes/1
- ct_ftp
  - Top of manual page
  - cd/2
  - close/1
  - delete/2
  - get/3
  - ls/2
  - open/1
  - put/3
  - recv/2
  - recv/3
  - send/2
  - send/3
  - type/2
- ct_ssh
  - Top of manual page
  - apread/4
  - apread/5
  - apwrite/4
  - apwrite/5
  - aread/3
  - aread/4
  - awrite/3
  - awrite/4
  - close/2
  - close/3
  - connect/1
  - connect/2
  - connect/3
  - del_dir/2
  - del_dir/3
  - delete/2
  - delete/3
  - disconnect/1
  - exec/2
  - exec/3
  - exec/4
  - get_file_info/2
  - get_file_info/3
  - list_dir/2
  - list_dir/3
  - make_dir/2
  - make_dir/3
  - make_symlink/3
  - make_symlink/4
  - open/3
  - open/4
  - opendir/2
  - opendir/3
  - position/3
  - position/4
  - pread/4
  - pread/5
  - pwrite/4
  - pwrite/5
  - read/3
  - read/4
  - read_file/2
  - read_file/3
  - read_file_info/2
  - read_file_info/3
  - read_link/2
  - read_link/3
  - read_link_info/2
  - read_link_info/3
  - receive_response/2
  - receive_response/3
  - receive_response/4
  - rename/3
  - rename/4
  - send/3
  - send/4
  - send/5
  - send_and_receive/3
  - send_and_receive/4
  - send_and_receive/5
  - send_and_receive/6
  - session_close/2
  - session_open/1
  - session_open/2
  - sftp_connect/1
  - subsystem/3
  - subsystem/4
  - write/3
  - write/4
  - write_file/3
  - write_file/4
  - write_file_info/3
  - write_file_info/4
- ct_rpc
  - Top of manual page
  - app_node/2
  - app_node/3
  - app_node/4
  - call/4
  - call/5
  - call/6
  - cast/4
  - cast/5
- ct_snmp
  - Top of manual page
  - get_next_values/3
  - get_values/3
  - load_mibs/1
  - register_agents/2
  - register_users/2
  - register_usm_users/2
  - set_info/1
  - set_values/4
  - start/2
  - start/3
  - stop/1
  - unregister_agents/1
  - unregister_users/1
  - update_usm_users/2
- ct_telnet
  - Top of manual page
  - close/1
  - cmd/2
  - cmd/3
  - cmdf/3
  - cmdf/4
  - cont_log/2
  - end_log/0
  - expect/2
  - expect/3
  - get_data/1
  - open/1
  - open/2
  - open/3
  - open/4
  - send/2
  - sendf/3
- unix_telnet
- ct_slave
  - Top of manual page
  - start/1
  - start/2
  - start/3
  - stop/1
  - stop/2
- ct_hooks
  - Top of manual page
  - Module:init/2
  - Module:pre_init_per_suite/3
  - Module:post_init_per_suite/4
  - Module:pre_init_per_group/3
  - Module:post_init_per_group/4
  - Module:pre_init_per_testcase/3
  - Module:post_end_per_testcase/4
  - Module:pre_end_per_group/3
  - Module:post_end_per_group/4
  - Module:pre_end_per_suite/3
  - Module:post_end_per_suite/4
  - Module:on_tc_fail/3
  - Module:on_tc_skip/3
  - Module:terminate/1
  - Module:id/1

# ct

### MODULE

ct

### MODULE SUMMARY

Main user interface for the Common Test framework.

### DESCRIPTION

Main user interface for the Common Test framework.

This module implements the command line interface for running tests and some basic functions for common test case issues such as configuration and logging.

Test Suite Support Macros

The config macro is defined in ct.hrl. This macro should be used to retrieve information from the Config variable sent to all test cases. It is used with two arguments, where the first is the name of the configuration variable you wish to retrieve, and the second is the Config variable supplied to the test case.

Possible configuration variables include:

- data_dir - Data file directory.

- priv_dir - Scratch file directory.

- Whatever added by init_per_suite/1 or init_per_testcase/2 in the test suite.

### DATA TYPES

handle() = handle() (see module ct_gen_conn) | term()

  The identity of a specific connection.

target_name() = var_name()

  The name of a target.

var_name() = atom()

  A variable name which is specified when ct:require/2 is called, e.g. ct:require(mynodename,{node,[telnet]})

### EXPORTS

abort_current_testcase(Reason) -> ok | {error, no_testcase_running}

Types:

Reason = term()

When calling this function, the currently executing test case will be aborted. It is the user's responsibility to know for sure which test case is currently executing. The function is therefore only safe to call from a function which has been called (or synchronously invoked) by the test case.

Reason, the reason for aborting the test case, is printed in the test case log.

add_config(Callback, Config) -> ok | {error, Reason}

Types:

Callback = atom()
Config = string()
Reason = term()

This function loads configuration variables using the given callback module and configuration string. Callback module should be either loaded or present in the code part. Loaded configuration variables can later be removed using remove_config/2 function.

comment(Comment) -> void()

Types:

Comment = term()

Print the given Comment in the comment field of the table on the test suite result page.

If called several times, only the last comment is printed. comment/1 is also overwritten by the return value {comment,Comment} or by the function fail/1 (which prints Reason as a comment).

decrypt_config_file(EncryptFileName, TargetFileName) -> ok | {error, Reason}

Types:

EncryptFileName = string()
TargetFileName = string()
Reason = term()

This function decrypts EncryptFileName, previously generated with encrypt_config_file/2/3. The original file contents is saved in the target file. The encryption key, a string, must be available in a text file named .ct_config.crypt in the current directory, or the home directory of the user (it is searched for in that order).

decrypt_config_file(EncryptFileName, TargetFileName, KeyOrFile) -> ok | {error, Reason}

Types:

EncryptFileName = string()
TargetFileName = string()
KeyOrFile = {key, string()} | {file, string()}
Reason = term()

This function decrypts EncryptFileName, previously generated with encrypt_config_file/2/3. The original file contents is saved in the target file. The key must have the the same value as that used for encryption.

encrypt_config_file(SrcFileName, EncryptFileName) -> ok | {error, Reason}

Types:

SrcFileName = string()
EncryptFileName = string()
Reason = term()

This function encrypts the source config file with DES3 and saves the result in file EncryptFileName. The key, a string, must be available in a text file named .ct_config.crypt in the current directory, or the home directory of the user (it is searched for in that order).

See the Common Test User's Guide for information about using encrypted config files when running tests.

See the crypto application for details on DES3 encryption/decryption.

encrypt_config_file(SrcFileName, EncryptFileName, KeyOrFile) -> ok | {error, Reason}

Types:

SrcFileName = string()
EncryptFileName = string()
KeyOrFile = {key, string()} | {file, string()}
Reason = term()

This function encrypts the source config file with DES3 and saves the result in the target file EncryptFileName. The encryption key to use is either the value in {key,Key} or the value stored in the file specified by {file,File}.

See the Common Test User's Guide for information about using encrypted config files when running tests.

See the crypto application for details on DES3 encryption/decryption.

fail(Reason) -> void()

Types:

Reason = term()

Terminate a test case with the given error Reason.

get_config(Required) -> Value

Equivalent to get_config(Required, undefined, []).

get_config(Required, Default) -> Value

Equivalent to get_config(Required, Default, []).

get_config(Required, Default, Opts) -> ValueOrElement

Types:

Required = KeyOrName | {KeyOrName, SubKey}
KeyOrName = atom()
SubKey = atom()
Default = term()
Opts = [Opt] | []
Opt = element | all
ValueOrElement = term() | Default

Read config data values.

This function returns the matching value(s) or config element(s), given a config variable key or its associated name (if one has been specified with require/2 or a require statement).

Example, given the following config file:

       {unix,[{telnet,IpAddr},
              {username,Username},
              {password,Password}]}.

get_config(unix,Default) -> [{telnet,IpAddr}, {username,Username}, {password,Password}]
get_config({unix,telnet},Default) -> IpAddr
get_config({unix,ftp},Default) -> Default
get_config(unknownkey,Default) -> Default

If a config variable key has been associated with a name (by means of require/2 or a require statement), the name may be used instead of the key to read the value:

require(myhost,unix) -> ok
get_config(myhost,Default) -> [{telnet,IpAddr}, {username,Username}, {password,Password}]

If a config variable is defined in multiple files and you want to access all possible values, use the all option. The values will be returned in a list and the order of the elements corresponds to the order that the config files were specified at startup.

If you want config elements (key-value tuples) returned as result instead of values, use the element option. The returned elements will then be on the form {KeyOrName,Value}, or (in case a subkey has been specified) {{KeyOrName,SubKey},Value}

See also: get_config/1, get_config/2, require/1, require/2.

get_status() -> TestStatus | {error, Reason} | no_tests_running

Types:

TestStatus = [StatusElem]
StatusElem = {current, {Suite, TestCase}} | {successful, Successful} | {failed, Failed} | {skipped, Skipped} | {total, Total}
Suite = atom()
TestCase = atom()
Successful = integer()
Failed = integer()
Skipped = {UserSkipped, AutoSkipped}
UserSkipped = integer()
AutoSkipped = integer()
Total = integer()
Reason = term()

Returns status of ongoing test. The returned list contains info about which test case is currently executing, as well as counters for successful, failed, skipped, and total test cases so far.

get_target_name(Handle) -> {ok, TargetName} | {error, Reason}

Types:

Handle = handle()
TargetName = target_name()

Return the name of the target that the given connection belongs to.

install(Opts) -> ok | {error, Reason}

Types:

Opts = [Opt]
Opt = {config, ConfigFiles} | {event_handler, Modules} | {decrypt, KeyOrFile}
ConfigFiles = [ConfigFile]
ConfigFile = string()
Modules = [atom()]
KeyOrFile = {key, Key} | {file, KeyFile}
Key = string()
KeyFile = string()

Install config files and event handlers.

Run this function once before first test.

Example:
install([{config,["config_node.ctc","config_user.ctc"]}]).

Note that this function is automatically run by the ct_run program.

listenv(Telnet) -> [Env]

Types:

Telnet = term()
Env = {Key, Value}
Key = string()
Value = string()

Performs the listenv command on the given telnet connection and returns the result as a list of Key-Value pairs.

log(Format) -> ok

Equivalent to log(default, Format, []).

log(X1, X2) -> ok

Types:

X1 = Category | Format
X2 = Format | Args

Equivalent to log(Category, Format, Args).

log(Category, Format, Args) -> ok

Types:

Category = atom()
Format = string()
Args = list()

Printout from a testcase to the log.

This function is meant for printing stuff directly from a testcase (i.e. not from within the CT framework) in the test log.

Default Category is default and default Args is [].

pal(Format) -> ok

Equivalent to pal(default, Format, []).

pal(X1, X2) -> ok

Types:

X1 = Category | Format
X2 = Format | Args

Equivalent to pal(Category, Format, Args).

pal(Category, Format, Args) -> ok

Types:

Category = atom()
Format = string()
Args = list()

Print and log from a testcase.

This function is meant for printing stuff from a testcase both in the log and on the console.

Default Category is default and default Args is [].

parse_table(Data) -> {Heading, Table}

Types:

Data = [string()]
Heading = tuple()
Table = [tuple()]

Parse the printout from an SQL table and return a list of tuples.

The printout to parse would typically be the result of a select command in SQL. The returned Table is a list of tuples, where each tuple is a row in the table.

Heading is a tuple of strings representing the headings of each column in the table.

print(Format) -> ok

Equivalent to print(default, Format, []).

print(X1, X2) -> term()

Equivalent to print(Category, Format, Args).

print(Category, Format, Args) -> ok

Types:

Category = atom()
Format = string()
Args = list()

Printout from a testcase to the console.

This function is meant for printing stuff from a testcase on the console.

Default Category is default and default Args is [].

reload_config(Required) -> ValueOrElement

Types:

Required = KeyOrName | {KeyOrName, SubKey}
KeyOrName = atom()
SubKey = atom()
ValueOrElement = term()

Reload config file which contains specified configuration key.

This function performs updating of the configuration data from which the given configuration variable was read, and returns the (possibly) new value of this variable.

Note that if some variables were present in the configuration but are not loaded using this function, they will be removed from the configuration table together with their aliases.

remove_config(Callback, Config) -> ok

Types:

Callback = atom()
Config = string()
Reason = term()

This function removes configuration variables (together with their aliases) which were loaded with specified callback module and configuration string.

require(Required) -> ok | {error, Reason}

Types:

Required = Key | {Key, SubKeys}
Key = atom()
SubKeys = SubKey | [SubKey]
SubKey = atom()

Check if the required configuration is available.

Example: require the variable myvar:
ok = ct:require(myvar)

In this case the config file must at least contain:

       {myvar,Value}.

Example: require the variable myvar with subvariable sub1:
ok = ct:require({myvar,sub1})

In this case the config file must at least contain:

       {myvar,[{sub1,Value}]}.

See also: get_config/1, get_config/2, get_config/3, require/2.

require(Name, Required) -> ok | {error, Reason}

Types:

Name = atom()
Required = Key | {Key, SubKeys}
Key = atom()
SubKeys = SubKey | [SubKey]
SubKey = atom()

Check if the required configuration is available, and give it a name.

If the requested data is available, the main entry will be associated with Name so that the value of the element can be read with get_config/1,2 provided Name instead of the Key.

Example: Require one node with a telnet connection and an ftp connection. Name the node a:
ok = ct:require(a,{node,[telnet,ftp]}).
All references to this node may then use the node name. E.g. you can fetch a file over ftp like this:
ok = ct:ftp_get(a,RemoteFile,LocalFile).

For this to work, the config file must at least contain:

       {node,[{telnet,IpAddr},
              {ftp,IpAddr}]}.

See also: get_config/1, get_config/2, get_config/3, require/1.

run(TestDirs) -> Result

Types:

TestDirs = TestDir | [TestDir]

Run all testcases in all suites in the given directories.

See also: run/3.

run(TestDir, Suite) -> Result

Run all testcases in the given suite.

See also: run/3.

run(TestDir, Suite, Cases) -> Result

Types:

TestDir = string()
Suite = atom()
Cases = atom() | [atom()]
Result = [TestResult] | {error, Reason}

Run the given testcase(s).

Requires that ct:install/1 has been run first.

Suites (*_SUITE.erl) files must be stored in TestDir or TestDir/test. All suites will be compiled when test is run.

run_test(Opts) -> Result

Types:

Opts = [OptTuples]
OptTuples = {dir, TestDirs} | {suite, Suites} | {group, Groups} | {testcase, Cases} | {spec, TestSpecs} | {label, Label} | {config, CfgFiles} | {userconfig, UserConfig} | {allow_user_terms, Bool} | {logdir, LogDir} | {silent_connections, Conns} | {stylesheet, CSSFile} | {cover, CoverSpecFile} | {step, StepOpts} | {event_handler, EventHandlers} | {include, InclDirs} | {auto_compile, Bool} | {multiply_timetraps, M} | {scale_timetraps, Bool} | {repeat, N} | {duration, DurTime} | {until, StopTime} | {force_stop, Bool} | {decrypt, DecryptKeyOrFile} | {refresh_logs, LogDir} | {basic_html, Bool} | {ct_hooks, CTHs}
TestDirs = [string()] | string()
Suites = [string()] | string()
Cases = [atom()] | atom()
Groups = [atom()] | atom()
TestSpecs = [string()] | string()
Label = string() | atom()
CfgFiles = [string()] | string()
UserConfig = [{CallbackMod, CfgStrings}] | {CallbackMod, CfgStrings}
CallbackMod = atom()
CfgStrings = [string()] | string()
LogDir = string()
Conns = all | [atom()]
CSSFile = string()
CoverSpecFile = string()
StepOpts = [StepOpt] | []
StepOpt = config | keep_inactive
EventHandlers = EH | [EH]
EH = atom() | {atom(), InitArgs} | {[atom()], InitArgs}
InitArgs = [term()]
InclDirs = [string()] | string()
M = integer()
N = integer()
DurTime = string(HHMMSS)
StopTime = string(YYMoMoDDHHMMSS) | string(HHMMSS)
DecryptKeyOrFile = {key, DecryptKey} | {file, DecryptFile}
DecryptKey = string()
DecryptFile = string()
CTHs = [CTHModule | {CTHModule, CTHInitArgs}]
CTHModule = atom()
CTHInitArgs = term()
Result = [TestResult] | {error, Reason}

Run tests as specified by the combination of options in Opts. The options are the same as those used with the ct_run program. Note that here a TestDir can be used to point out the path to a Suite. Note also that the option testcase corresponds to the -case option in the ct_run program. Configuration files specified in Opts will be installed automatically at startup.

run_testspec(TestSpec) -> Result

Types:

TestSpec = [term()]

Run test specified by TestSpec. The terms are the same as those used in test specification files.

sleep(Time) -> ok

Types:

Time = {hours, Hours} | {minutes, Mins} | {seconds, Secs} | Millisecs | infinity
Hours = integer()
Mins = integer()
Secs = integer()
Millisecs = integer() | float()

This function, similar to timer:sleep/1, suspends the test case for specified time. However, this function also multiplies Time with the 'multiply_timetraps' value (if set) and under certain circumstances also scales up the time automatically if 'scale_timetraps' is set to true (default is false).

start_interactive() -> ok

Start CT in interactive mode.

From this mode all test case support functions can be executed directly from the erlang shell. The interactive mode can also be started from the OS command line with ct_run -shell [-config File...].

If any functions using "required config data" (e.g. telnet or ftp functions) are to be called from the erlang shell, config data must first be required with ct:require/2.

Example:
> ct:require(unix_telnet, unix).
ok
> ct_telnet:open(unix_telnet).
{ok,<0.105.0>}
> ct_telnet:cmd(unix_telnet, "ls .").
{ok,["ls","file1 ...",...]}

step(TestDir, Suite, Case) -> Result

Types:

Case = atom()

Step through a test case with the debugger.

See also: run/3.

step(TestDir, Suite, Case, Opts) -> Result

Types:

Case = atom()
Opts = [Opt] | []
Opt = config | keep_inactive

Step through a test case with the debugger. If the config option has been given, breakpoints will be set also on the configuration functions in Suite.

See also: run/3.

stop_interactive() -> ok

Exit the interactive mode.

See also: start_interactive/0.

testcases(TestDir, Suite) -> Testcases | {error, Reason}

Types:

TestDir = string()
Suite = atom()
Testcases = list()
Reason = term()

Returns all testcases in the specified suite.

timetrap(Time) -> ok

Types:

Time = {hours, Hours} | {minutes, Mins} | {seconds, Secs} | Millisecs | infinity
Hours = integer()
Mins = integer()
Secs = integer()
Millisecs = integer() | float()

Use this function to set a new timetrap for the running test case.

userdata(TestDir, Suite) -> SuiteUserData | {error, Reason}

Types:

TestDir = string()
Suite = atom()
SuiteUserData = [term()]
Reason = term()

Returns any data specified with the tag userdata in the list of tuples returned from Suite:suite/0.

userdata(TestDir, Suite, Case) -> TCUserData | {error, Reason}

Types:

TestDir = string()
Suite = atom()
Case = atom()
TCUserData = [term()]
Reason = term()

Returns any data specified with the tag userdata in the list of tuples returned from Suite:Case/0.