curl/tests/data/test1007
Dan Fandrich 72c5bb14e7 tests: improve reliability of TFTP tests
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
2023-06-19 17:10:24 -07:00

48 lines
680 B
Plaintext

<testcase>
<info>
<keywords>
TFTP
TFTP WRQ
FAILURE
</keywords>
</info>
#
# Client-side
<client>
<server>
tftp
</server>
<name>
TFTP send with invalid permission on server
</name>
<command>
-T %LOGDIR/test%TESTNUMBER.txt tftp://%HOSTIP:%TFTPPORT//invalid-file -sS
</command>
<file name="%LOGDIR/test%TESTNUMBER.txt">
This data will not be sent
</file>
</client>
#
# Verify pseudo protocol after the test has been "shot"
<verify>
<errorcode>
69
</errorcode>
<strip>
^timeout = [5-6]$
</strip>
<protocol>
opcode = 2
mode = octet
tsize = 27
blksize = 512
filename = /invalid-file
</protocol>
<stderr mode="text">
curl: (69) TFTP: Access Violation
</stderr>
</verify>
</testcase>