| Age | Commit message (Collapse) | Author |
|---|
|
If ssh_connection:adjust_window/3 is not called after each time data
is received in the netconf client, the client will eventually stop
receiving data. This bug has been corrected.
|
|
Conflicts:
lib/common_test/test/Makefile
|
|
|
|
|
|
|
|
The following corrections/changes are done in the cth_surefire hook:
* Earlier there would always be a 'properties' element under the
'testsuites' element. This would exist even if there were now
'property' element inside it. This has been changed so if there are
no 'property' elements to display, then there will not be a
'properties' element either.
* The XML file will now (unless other is specified) be stored in the
top log directory. Earlier, the default directory would be the
current working directory for the erlang node, which would mostly,
but not always, be the top log directory.
* The 'hostname' attribute in the 'testsuite' element would earlier
never have the correct value. This has been corrected.
* The 'errors' attribute in the 'testsuite' element would earlier
display the number of failed testcases. This has been changed and
will now always have the value 0, while the 'failures' attribute
will show the number of failed testcases.
* A new attribute 'skipped' is added to the 'testsuite' element. This
will display the number of skipped testcases. These would earlier be
included in the number of failed test cases.
* The total number of tests displayed by the 'tests' attribute in the
'testsuite' element would earlier include init/end_per_suite and
init/end_per_group. This is no longer the case. The 'tests'
attribute will now only count "real" test cases.
* Earlier, auto skipped test cases would have no value in the 'log'
attribute. This is now corrected.
* A new attributes 'log' is added to the 'testsuite' element.
* A new option named 'url_base' is added for this hook. If this
option is used, a new attribute named 'url' will be added to the
'testcase' and 'testsuite' elements.
Tests are added for the ct_surefire hook.
|
|
* egil/fix-dialyzer-specs/OTP-10601:
common_test: Fix exported types
|
|
* inet:host_name() -> inet:hostname()
* ct:hook_options() -> ct_netconfc:hook_options()
|
|
The R15B03 release
|
|
|
|
* bjorn/ct/env-vars/OTP-10469:
Add support for passing environment variables in master mode
Remove redundant sleep in ct_master_SUITE
Test that test cases succeed
Add ct_test_support:verify_events/4 which takes a node name
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
lib/common_test/test/Makefile
|
|
* origin/peppe/common_test/group_search_r15b03:
Fix problem with test case order in group specifications
Finish the test suite and correct remaining bugs
Implement new group search functionality
OTP-10466
|
|
|
|
|
|
OTP-10466
|
|
OTP-10466
|
|
OTP-10495
|
|
|
|
* siri/common_test/ct_netconfc-close-problems:
[common_test] Allow server to terminate netconf session before rpc-reply
[common_test] Ensure process down after ct_netconf:close_session
|
|
test_server_h will now recognize info_reports written by ct connection
handlers (according to the description in cth_conn_log) and ignore
them as they will be completely handled by by ct_conn_log_h.
Earlier test_server_h would print a tag (testcase name) before
forwarding the report to error_logger_tty_h. This would cause lots of
tags in the log with no info report following (since
error_logger_tty_h did not handle them).
|
|
OTP-10570
ct_netconfc:close_session sometimes returned {error,closed} because
the ssh connection was closed (from the server side) before the
rpc-reply was received by the client. This is normal and can not be
helped. It has been corrected so the return will be 'ok' in this case.
Other error situations will still give {error,Reason}.
|
|
OTP-10510
When starting a named netconf connection directly after stopping one
with the same name, it sometimes failed with 'connection_exists'. This
has been corrected.
|
|
* maint:
Fix bug where require of same name at same config would return name in use
|
|
|
|
ct:abort_current_testcase/1 (which is a wrapper for the function
with the same name in test_server_ctrl) would not work as expected
when a group with parallel test cases was executing. Essentially,
the abort_current_testcase message would be ignored until the group
has finished and would then abort the end_per_group testcase for
the group.
Since there is no unique current testcase when a parallel group is
executing, we must handle the abort_current_testcase message and
return an error tuple.
Also fix the bug that test_server_ctrl:abort_current_testcase/1
would always return 'ok'.
|
|
|
|
* maint:
Skip ct_netconf tests if there is no crypto
Migrate timers from test_server to ct interface
Update tests to run with an oldshell emulator
Move crypto check so that tc is skipped and not failed
Update for new version of ppc compilation chain
Verify that ebin folder of applications exists
Conflicts:
lib/asn1/test/asn1_SUITE.erl
lib/kernel/test/interactive_shell_SUITE.erl
|
|
* siri/cover-tests: (21 commits)
[common_test] Extend timer for flushing error logger
[cover] Allow reconnection if node has been disconnected or down
[cover] Don't kill remote nodes when connection to main node is lost
[test_server] Add option {start_cover,false} to test_server:start_node
Use code:lib_dir instead of code:which to get application directory
[common_test] Add test for OTP-9956
Include all kernel modules in code coverage analysis
[common_test] Add test suite for code coverage support
[common_test, test_server] Don't flush cover if cover is not running
[common_test] Add option cover_stop
[test_server] Allow cross cover analysis when testing through common_test
[test_server] Start cover in test_server:wait_for_node
[test_server] Multiply timers with timetrap_scale_factor when starting nodes
Include all stdlib modules in code coverage analysis
[test_server] Include all test_server modules in code coverage analysis
Skip epp_SUITE:otp_8911 if cover is running
[common_test] Start cover on slave nodes if running cover tests
[common_test] Don't stop cover before stopping slave node
[test_server] Don't stop cover after test is finished
[cover] Add support for test_server
...
OTP-10427
|
|
Because of a forgotten "Fd", configuration information intended for
ct_master_log.html ended up being written to standard output.
|
|
Prototype-by: Magnus Lidén <[email protected]>
|
|
|
|
|
|
|
|
OTP-10040
If a busy test case generated lots of error messages,
cth_log_redirect:post_end_per_testcase would crash with a timeout
while waiting for the error logger to finish handling all error
messages. The default timer is 5 seconds. This has now been extended
to 5 minutes.
|
|
OTP-9956
Test that the test suite itself can be cover compiled, and that
data_dir is still set correctly.
|
|
|
|
ct_slave, ct_test_support and test_server_test_lib always called
cover:flush/1 when stopping slave nodes. If cover was not running,
this would cause cover_server to be started and thus
test_server:is_cover/0 to return true afterwards. This has been
corrected.
|
|
By default, test_server will always stop cover (and thus load back the
non cover compiled original beam files) after a test with code
coverage analysis is completed. The new option allows the common_test
user to specify that cover shall not be stopped. This can be useful if
there are processes still running old code, i.e. processes that have
not done any fully qualified function call after the cover
compilation, since loading the original code then will kill those
processes. This is only recommended if the erlang node is to be
stopped after the test run, or if cover can be manually stopped.
|
|
The cross cover analysis functionality in test_server was broken since
OTP converted to running daily tests through common_test. This has
been corrected.
|
|
Nodes started with ct_slave should automatically run cover when tests
are executed with cover analysis. Nodes must also be flushed for cover
data before stopped.
|
|
In order to avoid crash of processes that hold old code, cover is no
longer stopped before slave nodes are stopped. Instead cover:flush is
used which only fetches cover data from the slave.
This, along with similar changes in test_server allows all common_test
modules to be included in cover analysis.
|
|
|
|
|
