Age | Commit message (Collapse) | Author |
|
By default, each command is appended with "\n", but in some cases a
command must end with "\r\n" to evaluate correctly. This can now be
specified with option {newline,"\r\n"}.
|
|
|
|
ct_telnet_own_server_SUITE:large_string tests that the client can
receive a chopped up string. To make sure the right thing is tested, a
SHORT timer is used before calling ct_telnet:get_data, but on some
slow machines the the timer is too short to allow data to be
received. To overcome this, the test now re-tries ct_telnet:get_data a
few times before giving up.
|
|
OTP-12688
|
|
|
|
OTP-12335
|
|
This test case simulates that the server spontaneously sends data. By
changing ct_telnet:send to ct_telnet_client:send_data this simulations
makes more sense - since client's buffers are not flushed.
Also removed the newline at the end of "echo_no_prompt" command. Since
newline is added automatically, the explicit newline at the end of the
command causes a prompt to be sent which is not expected.
|
|
This is for stabilizing test cases.
|
|
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}]).
|
|
OTP-11871
|
|
|
|
|
|
|
|
|
|
|
|
Also fix remaining problems in source code
|
|
Also correct some issues found during test
|
|
|
|
The symptom of this bug was that a (named) telnet connection which was
open and hanging during a timetrap timeout could no longer be opened
again in subsequent test cases.
Since the connection was hanging, ct_telnet:close/1 which was called
during end_per_testcase would fail (timeout) and cause common_test to
brutally kill the connection. The bug was that the connection was not
unregistered at this point. When trying to open the connection again
in the next testcase, common_test attempted to reuse the same
connection since it had not been unregistered. This failed since the
connection in fact was dead.
|
|
If this option is used, ct_telnet will not search for a prompt before
attempting to match the given pattern. This is useful if, for
instance, the Pattern itself matches the prompt or if the telnet
session starts interactive programs which do not display the normal
prompt.
|
|
The new test suite ct_telnet_SUITE_data/ct_telnet_own_server_SUITE
uses the very simple telnet_server.erl located in the common_test test
directory.
|
|
user and password.
|