| Age | Commit message (Collapse) | Author |
|---|
|
ct_telnet by default adds a newline to all command strings before
sending to the telnet server. In some situations this is not desired,
for example when sending telnet command sequences (prefixed with the
Interprete As Command, IAC, character). In such cases, the new option
can be used. Example - send an Are Your There (AYT) sequence:
ct_telnet:send(Connection, [255,246], [{newline,false}]).
|
|
... when two tests are run within the same test case.
|
|
5a3c4668 accidentially changed the base directory for cover export
and import files, if given as relative paths. This commit fixes this -
the files are again expected to be given relative to the directory of
the cover spec file itself, or else as absolute paths.
|
|
|
|
This addresses several bugs in common_test (ct) when using the cover
analysis mechanism:
In a ct test run, one can give a cover spec file which indicates that
cover analysis shall be run, including a number of modules and a
number of nodes. During the ct test run, multiple jobs may be started
in test_server, and when the cover option is used, test_server would
cover compile and analyse all given modules for each job. This commit
instead allows the compilation and analysis to be explicitly ordered
by ct for each test run. This way each module will only be cover
compiled and analysed once. The cover log will be located in the
common_test log directory (ct_run.<timestamp>), and the "Coverage log"
link in each suite.log.html will point to this file. A new button is
also added in the top level ct index file, which points to the cover
log.
This change also reduces the need of using the 'export' and 'import'
options, since there is no longer any need to accumulate cover data
over multiple test_server jobs. However, these options may still be
used for importing and exporting cover data in order to store or
accumulate data from multiple ct test runs.
The 'nodes' option was earlier only used by ct to start cover on the
given nodes before starting the first test_server job. After this job
was completed, test_server would stop cover completely and then start
it again for the next job without any knowledge of the 'nodes'
options. For the next test_server jobs cover would therefore no longer
be running on these nodes. Explcit calls to ct_cover:add_nodes had to
be done in order to collect data through all test_server jobs. This
bug has now been solved, since cover is no longer stopped between each
test_server job.
Finally, ct no longer stores cover data using
ct_util:set_testdata. This was earlier used by ct_cover:add_nodes to
make sure no node was added twice.This did, however, cause some
problems when ct and cover were out of sync. ct could belive that a
node was running cover and thus reject adding this node, while in
reality cover had been stopped on the node (e.g. by test_server) so no
cover data was collected. ct_cover:add_nodes will now instead use
cover:which_nodes to check if a node is already running.
|
|
|
|
OTP-11871
|
|
OTP-11440
|
|
* peppe/common_test/telnet_expect_timeout:
Add test cases
Introduce total timeout value in ct_telnet:expect/3 options
OTP-11689
|
|
|
|
|
|
* origin/peppe/common_test/telnet_logging_final:
Add test cases and fix some problems with logging and with the telnet client
Get ct_telnet_client to print all data from server to log
Change telnet logging behaviour
OTP-11690
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also fix remaining problems in source code
|
|
Also correct some issues found during test
|
|
|
|
* peppe/common_test/hook_skip_failure:
Fix CT hook pre_end_per_group causing crash when returning {skip,Reason}
OTP-11409
|
|
OTP-11409
|
|
* siri/ct_netconfc/close_session-timeout-hangs/OTP-11478:
[common_test] Don't hang netconf client when close-session times out
|
|
* siri/cuddle-with-tests:
[observer] Fix copy/paste error in observer_SUITE:app_file/1
[common_test] Minor corrections in test of ct_netconfc
|
|
* origin/peppe/common_test/change_skip_behaviour:
Modify the auto_skip report for group config funcs to include group name
Fix problems with info functions and add more tests
Add test cases for new and modified functionality
Fix problem with suites and groups skipped from test specification
Change report tag for failed init_per_testcase from skipped to auto_skipped
Add tests for skipping parallel groups
Correct tests cases that fail because of modified events
Correct various bugs related to auto_skip and groups
Change status from skip to auto_skip for config func that fails due to require
Fix problem with handling Config and FW reports correctly
Change skip vs auto_skip behaviour
OTP-11305
|
|
|
|
When the netconf server did not respond to the close-session request,
the call to ct_netconfc:close_session/2 would hang forever waiting for
the netconf client to terminate. This has been corrected. The client
will now always terminate (and take down the connection) if the
close-session request times out.
|
|
Also correct failing test cases and find and fix remaining bugs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* origin/peppe/common_test/cth_ctrl:
Find and fix minor bugs
Add test suite
Fix timing related problem
Fix problem with start order of hooks and stopping of ct_util_server
Introduce pre- and post-test i/o log
OTP-11272
|
|
|
|
|
|
|
|
OTP-11238
|
|
* origin/peppe/common_test/ct_log_updates:
Make the CT logger print to stdout if test_server is not running
Add test
Allow calls to ct:pal and ct:print even if CT is not running
OTP-11176
|
|
OTP-11176
|
|
ct_netconfc:create_subscription only allows one XML element inside the
'filter' element. According to RFC5277 it should be allowed to add any
number of elements inside the filter, so this is now corrected.
|
