| Age | Commit message (Collapse) | Author |
|---|
|
This is to allow slower test hosts.
|
|
|
|
The test case cover_SUITE:slave_start_slave often fails on a test host
(windows) due to a hanging node from an earlier test run. In the first
test, the slave fails to start (boot_timeout?) and is never connected
to the test node. The attempt at cleaning up used nodes() to find
which slaves to kill - so in the case where the slave was never
connected it was never killed. This is no changed so each slave is
explicitly killed by name - no matter if it is pingable or not.
|
|
|
|
* peppe/common_test/log_cache:
Implement cache for the CT logger
OTP-10855
|
|
OTP-10855
|
|
|
|
* siri/common_test/force_stop-skip_rest/OTP-10856:
[common_test] Document '-force_stop skip_rest' option to ct_run
[common_test] Add tests for repeated testruns
[common_test] Add support for testing repeated testruns
[common_test] Add -force_stop skip_rest option when repeating tests
|
|
ct_repeate_testrun_SUITE is added, which tests the following options
to ct_run:
-repeat N
-duration [-force_stop [skip_rest]]
-until [-force_stop [skip_rest]]
|
|
user and password.
|
|
ct_test_support which is used in common_test's own tests did not
support testruns with -repeat, -duration or -until options. This is
now added.
|
|
Also, rename some nodes to avoid node name clash between test cases,
and ensure proper cleanup of nodes.
|
|
|
|
|
|
|
|
|
|
|
|
* peppe/common_test/testspec_include:
Fix failing test case
OTP-9881
|
|
OTP-9881
|
|
* peppe/common_test/testspec_include:
Fix problem with tests running in wrong order
OTP-9881
|
|
OTP-9881
|
|
* origin/peppe/common_test/restore_config:
Add verification terms in test suite
Add test case to verify that config data gets properly restored
OTP-10070
|
|
* peppe/common_test/testspec_include:
Add more tests
Update documentation
Add tests and correct errors
Update CT Master
Implement support for including test specifications
Make it possible to execute one test run per test specification
Conflicts:
lib/common_test/src/ct_master.erl
lib/common_test/src/ct_run.erl
lib/common_test/src/ct_testspec.erl
OTP-9881
|
|
|
|
* siri/unicode:
[test_server] Don't escape : and @ in test log links
[test_server] Don't create latin1 filenames if filename mode is utf8
[test_server] Ensure correct encoding in header for erl2html2:convert
[common_test] Update common test modules to handle unicode
[ts] Use unicode:characters_to_list/2 instead of binary_to_list/1
[test_server] Add tests for unicode support
[test_server] Write link target with correct encoding in erl2html2
[test_server] Update test_server to handle unicode
Update preloaded init.beam
Make arguments given with -s option to erl aware of file name encoding
OTP-10702
OTP-10783
|
|
|
|
* Use UTF-8 encoding for all HTML files, except the HTML version of
the test suite generated with erl2html2:convert, which will have the
same encoding as the original test suite (.erl) file.
* Encode link targets in HTML files with
test_server_ctrl:uri_encode/1.
* Use unicode modifier 't' with ~s when appropriate.
* Use unicode:characters_to_list and unicode:characters_to_binary for
conversion between binaries and strings instead of binary_to_list
and list_to_binary.
|
|
ct_surefire_SUITE:logdir/1 creates a directory named "specific_logdir"
which was never cleaned. This commit makes sure the directory exists
and is empty before the test case runs.
|
|
ct_surefire_SUITE erronously assumed that logs would always be located
under priv_dir, but this is not true on windows where logs are located
in temp dir. This has been corrected.
|
|
OTP-9881
|
|
OTP-9881
|
|
OTP-9881
|
|
OTP-9881
|
|
* siri/common_test/minor_test_fixes/OTP-10483:
[common_test] Extend timetrap time in ct_hooks_SUITE
[common_test] Avoid hanging ct@host node if crypto does not exist
[common_test] Changed call to publick_key to use documented interface
[common_test] Extend timeout values for slave nodes in ct_master_SUITE
[common_test] Extend valid interval for approximate timer values in tests
|
|
* siri/cross-cover/OTP-9870:
[test_server] Don't use print/3 in cross_cover_analyse
[common_test] Add documentation for cross cover analysis
[common_test] Add test case for cross cover mechanism
[test_server] Update documentation about cross cover
[test_server] Add test of code cover mechanism
[test_server,common_test] Fix cross cover mechansim
|
|
OTP-10070
|
|
|
|
Before terminating slave nodes, common_test calls cover:flush/1 to
fetch data from the node without actually stopping cover on this
node. If cover is not stopped for the node and a new node with the
same name is started, then cover will be started on the new node. To
avoid this common_test now calls cover:stop/1 after the slave node is
terminated.
|
|
Conflicts:
lib/common_test/test/Makefile
|
|
This suite often fails with timetrap timeout on some test machines.
|
|
ct_netconfc:init_per_suite called ct_test_support:init_per_suite
before checking if crypto exists. This caused the slave node (ct@host)
to be started even though the suite would be skipped when crypto did
not exist - which in turn caused a hanging ct node since end_per_suite
is not run in a skipped suite. This has been corrected.
|
|
Earlier used 'OTP-PUB-KEY':encode/2 - now public_key:der_encode/2 instead.
|
|
Some tests in ct_master_SUITE failed on some platforms with
boot_timeout when trying to start slave nodes. The default timeout
value was 3 seconds, and it is now extended to 10 seconds in these
tests.
To avoid similar errors with init_timeout and startup_timeout, these
are both exteded from 1 second default value to 10 seconds in this
test.
|
|
When matching the result of tests of timetrap timeouts, the actual
time is measured against the expected time, and an interval of +/- 2%
was seen as correct result. This turned out to fail on some platforms
and is now changed to 5%.
|
|
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.
|
|
|
|
Update the interface for cross cover analysis (collection of cover
data over multiple tests) so it can be used via common_test and
directly with test server.
The concept of 'application' in the cross cover interface is removed
and replaced with an arbitrary Tag=atom() which identifies a test run.
|
|
* 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
|
|
|
|
|
