72c5bb14e7
Stop checking the timeout used by the client under test (for most tests). The timeout will change if the TFTP test server is slow (such as happens on an overprovisioned CI server) because the client will retry and reduce its timeout, and the actual value is not important for most tests. test285 is changed a different way, by increasing the connect timeout. This improves test coverage by allowing the changed timeout value to be checked, but improves reliability with a carefully-chosen timeout that not only allows twice the time to respond as before, but also allows several retries before the client will change its timeout value. Ref: #11328
48 lines
589 B
Plaintext
48 lines
589 B
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
TFTP
|
|
TFTP WRQ
|
|
</keywords>
|
|
</info>
|
|
|
|
#
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
tftp
|
|
</server>
|
|
<name>
|
|
TFTP send
|
|
</name>
|
|
<command>
|
|
-T %LOGDIR/test%TESTNUMBER.txt tftp://%HOSTIP:%TFTPPORT// --connect-time 549
|
|
</command>
|
|
<file name="%LOGDIR/test%TESTNUMBER.txt">
|
|
a chunk of
|
|
data
|
|
sent
|
|
to server
|
|
</file>
|
|
</client>
|
|
|
|
#
|
|
# Verify pseudo protocol after the test has been "shot"
|
|
<verify>
|
|
<upload>
|
|
a chunk of
|
|
data
|
|
sent
|
|
to server
|
|
</upload>
|
|
<protocol>
|
|
opcode = 2
|
|
mode = octet
|
|
tsize = 32
|
|
blksize = 512
|
|
timeout = 10
|
|
filename = /test%TESTNUMBER.txt
|
|
</protocol>
|
|
</verify>
|
|
</testcase>
|