| Age | Commit message (Collapse) | Author |
|---|
|
Earlier there was no way to add optional parameters like
default-operation to an edit-config request sent with
ct_netconfc:edit_config/3,4, you had to use
ct_netconfc:send_rpc/2,3. For simplicity and completion, a new
optional argument, OptParams, is now added to the edit_config
function.
|
|
The new test is related to support sequence seq12645. It tests that
the netconf client process dies if the node hosting the netconf
server terminates.
|
|
* siri/ct_netconfc/close_session-timeout-hangs/OTP-11478:
[common_test] Don't hang netconf client when close-session times out
|
|
|
|
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.
|
|
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.
|
|
|
|
|
|
* 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.
|
|
Earlier used 'OTP-PUB-KEY':encode/2 - now public_key:der_encode/2 instead.
|
|
config
Tests failed with ehostunreach on some hosts since localhost could not
be resolved. CT configuration file for tests of ct_netconfc is now
changed to use 127.0.0.1 instead.
|
|
Some of the tests failed every now and then because an ets table in
the test netconf server was updated from different processes
simultaneously. Also, the same entries were used for multiple netconf
sessions. This has been corrected.
|
|
|
