diff options
author | Lukas Larsson <[email protected]> | 2012-08-09 18:00:13 +0200 |
---|---|---|
committer | Lukas Larsson <[email protected]> | 2012-08-23 16:18:53 +0200 |
commit | a71c6b976fa79fa3bcd0e61850a1a57071159b28 (patch) | |
tree | 0608f55c24792e551f4b0b3f291e062c46f24e4f /lib/common_test/doc/src/event_handler_chapter.xml | |
parent | 064b42237d891d5fdcb6c1a351980b8291437618 (diff) | |
download | otp-a71c6b976fa79fa3bcd0e61850a1a57071159b28.tar.gz otp-a71c6b976fa79fa3bcd0e61850a1a57071159b28.tar.bz2 otp-a71c6b976fa79fa3bcd0e61850a1a57071159b28.zip |
Update user config to use nested tuple keys
ct:get_config and ct:require can now use nested tuples
to fetch data from user configuration. E.g.
ct:get_config({localhost,ip,v4}).
This introduces a backwards incompatability with how names
are associated with keys when using require/2. E.g.
ct:require(a_name,{localhost,ip}) will associate a_name with ip
instead of localhost.
Diffstat (limited to 'lib/common_test/doc/src/event_handler_chapter.xml')
-rw-r--r-- | lib/common_test/doc/src/event_handler_chapter.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/common_test/doc/src/event_handler_chapter.xml b/lib/common_test/doc/src/event_handler_chapter.xml index a5886b9687..2f796b91ab 100644 --- a/lib/common_test/doc/src/event_handler_chapter.xml +++ b/lib/common_test/doc/src/event_handler_chapter.xml @@ -205,7 +205,7 @@ {error,{RunTimeError,StackTrace}} | {timetrap_timeout,integer()} | {failed,{Suite,end_per_testcase,FailInfo}}</c>, reason for failure.</p> - <p><c>RequireInfo = {not_available,atom()}</c>, why require has failed.</p> + <p><c>RequireInfo = {not_available,atom() | tuple()}</c>, why require has failed.</p> <p><c>FailInfo = {timetrap_timeout,integer()} | {RunTimeError,StackTrace} | UserTerm</c>, @@ -233,7 +233,7 @@ reason for auto skipping <c>Func</c>.</p> <p><c>FailReason = {Suite,ConfigFunc,FailInfo}} | {Suite,FailedCaseInSequence}</c>, reason for failure.</p> - <p><c>RequireInfo = {not_available,atom()}</c>, why require has failed.</p> + <p><c>RequireInfo = {not_available,atom() | tuple()}</c>, why require has failed.</p> <p><c>ConfigFunc = init_per_suite | init_per_group</c></p> <p><c>FailInfo = {timetrap_timeout,integer()} | {RunTimeError,StackTrace} | |