Age | Commit message (Collapse) | Author |
|
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.
|
|
When opening a connection, the connection process would link itself to
ct_util_server before calling the init callback, e.g. in ct_netconfc,
ct_telnet etc. If the init callback failed, then ct_util_server would
get the 'EXIT'. ct_util looks up the pid in the connection table, but
since the connection is not yet registered it is not found. ct_util
does not know which process it is and will thus die - aborting the
complete test run.
This commit moves the link(CtUtilServer) after the init callback, so a
crash in the init callback will not be detected by ct_util_server -
the caller process, however, will get a 'DOWN' message due to
monitoring and ct_gen_conn:start will give an error return.
|
|
Earlier, it was possible to open connection (ct_gen_conn) with the
same (required) name twice, which could give unexpected results. Such
attempts will now return {error,{connection_exists,OtherClient}}.
|
|
Earlier ct_util_server would terminate and thus abort the complete
test run if a connection process (ct_gen_conn) crashed. This is now
changed so that ct_util will only print an error report (in the test
case log) and continue the rest of the test.
|
|
The netconf client supports basic netconf functionality over SSH. In
order to allow testing of both success and failure cases, it is
intentionally written to allow non-standard behavior.
In order for the netconf client to use the generic connection
mechanism in common_test, ct_gen_conn has been updated to be more
flexible:
Added options:
{reconnect,bool()}
{forward_messages,bool()}
{use_existing_connection,bool()}
Allow handle_msg to return
{reply,Reply,State} |
{noreply,State} |
{stop,Reply,State}
If forward_messages==true, the ct_gen_conn callback must also
implement:
handle_msgs(Msg,State) -> {noreply,State} | {stop,State}
|
|
* lukas/common_test/surefire_fix_skipped_end/OTP-10158:
Fix bug where auto skipped tcs would disappear
Allow non configlist returns from other cths
Fix close of suite when end_per_suite is skipped
|
|
|
|
OTP-10106
OTP-10107
|
|
|
|
|
|
|
|
|
|
* origin/peppe/common_test/otp-9988_9871.merged:
Fix various problems with the user timetrap implementation
Fix dialyzer reported errors
Implement support for user controlled timetraps
OTP-9988
|
|
* origin/peppe/common_test/otp-9973:
Update ct_master to use the Common Test CSS file for the logs
OTP-9973
|
|
* origin/peppe/common_test/otp-10011:
Document the create_priv_dir option for ct:run_test/1
|
|
'lukas/common_test/fix_disable_builtin_hooks_from_spec/OTP-10009' into maint
* lukas/common_test/fix_disable_builtin_hooks_from_spec/OTP-10009:
Change default of enable builtin hooks to undefined
Disable built in hooks for emulator
|
|
peppe/common_test/otp-9988_9871.merged
Conflicts:
lib/common_test/src/ct_framework.erl
|
|
|
|
OTP-9973
|
|
|
|
* lukas/common_test/add_surefire_hook/OTP-9995:
Add the surefire ct hook
|
|
|
|
OTP-9988
|
|
The hook should work with modern versions of Jenkins CI
to gather test results.
|
|
OTP-9989
Also improve ct_hooks test suite.
|
|
|
|
|
|
Now that calls to ct_framework:init/end_per_suite take place
whenever init/end_per_suite is missing in the test suite,
these calls should trigger init/end_tc to perform configuration
(such as calling calling CTH functions, suite/0, etc).
|
|
OTP-9986
|
|
|
|
* origin/peppe/common_test/otp-9634_9659:
Change the option name 'unique_priv_dir' to 'create_priv_dir'
Add test suite for the unique_priv_dir feature
Make it possible to use unique priv_dir names
Create entry for every repeated test in index.html
OTP-9634
OTP-9659
|
|
* origin/peppe/common_test/otp-9899:
Fix broken repeat functionality
OTP-9899
|
|
* origin/peppe/common_test/otp-9964_9975_9595:
Have ct_run clean up the code path after each test run
Fix problems with ct_run's code path manipulation
OTP-9964
OTP-9975
OTP-9595
|
|
The new values for create_priv_dir are:
auto_per_run, auto_per_tc, manual_per_tc
|
|
|
|
Introduce the optional feature to have Test Server generate
priv_dir directory names that are unique for each test case
or config function. The name of the option/flag is
'unique_priv_dir' and it can be set to value 'auto' or
'manual'. If auto, Test Server creates each priv_dir
automatically (can be expensive in case of many and/or repeated
cases). If manual, the user needs to create the priv_dir
explicitly by calling ct:make_priv_dir/0.
|
|
For each repeated test during a test run, an entry is created
in the index.html file (i.e. the overview file for the test run).
In the top level (logdir) index file, only the last test result is
listed.
E.g, given the test spec:
[{merge_tests,false},{dirs,testobj1},{dirs,testobj1}]
In the index file for the test run (under Logdir/ct_run.Node.Date.Time),
both dir tests are listed. In the top level index file (under Logdir),
only the last test is listed (one has to find all results through the
all_runs.html file).
|
|
* origin/peppe/common_test/otp-9904_9900:
Introduce error notification printout in the tc log
OTP-9904
OTP-9900
|
|
OTP-9899
|
|
OTP-9595
|
|
OTP-9964
OTP-9975
|
|
Also fix problem with parallel test cases printing "into each other"
(when using ct:print or ct:pal).
OTP-9904
OTP-9900
|
|
OTP-9830
|
|
OTP-9933
|
|
* origin/peppe/common_test/otp-9941-9955:
Fix problem with handling error_logger events
OTP-9941
OTP-9955
|
|
OTP-9941
OTP-9955
|
|
|
|
In order to avoid possible deadlock when the cth_log_redirect hook
prints via ct_logs to the test case log file, the print call must
be made by a separate (temporary) process, instead of ct_logs.
|
|
|
|
* origin/peppe/common_test/capture_io:
Fix error in documentation
Create ct interface to the test_server:capture_* functions
OTP-9775
|