curl/tests/data/test190

<testcase>
<info>
<keywords>
FTP
</keywords>
</info>

# Server-side
<reply>
<servercmd>
DELAY CWD 60
</servercmd>
</reply>

# Client-side
<client>
<server>
ftp
</server>
<killserver>
ftp
</killserver>
 <name>
FTP download with strict timeout and slow CWD
 </name>
 <command timeout="1">
ftp://%HOSTIP:%FTPPORT/path/to/file/190 -m %FTPTIME2
</command>
</client>

# Verify data after the test has been "shot"
<verify>
# 28 is CURLE_OPERATION_TIMEDOUT
<errorcode>
28
</errorcode>
<protocol>
USER anonymous
PASS ftp@example.com
PWD
CWD path
</protocol>
</verify>
</testcase>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`<testcase>`
Add FTP keywords for a couple of currently keyword-less FTP tests 2012-11-16 06:42:51 -05:00			`<info>`
			`<keywords>`
			`FTP`
			`</keywords>`
			`</info>`

new tests 2001-11-02 18:09:02 -05:00			`# Server-side`
			`<reply>`
Various test file cleanups, including using <servercmd> instead of writing directly to ftpserver.cmd and removing unneeded empty sections. 2007-04-18 16:22:01 -04:00			`<servercmd>`
			`DELAY CWD 60`
			`</servercmd>`
new tests 2001-11-02 18:09:02 -05:00			`</reply>`

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 16:25:39 -04:00			`<server>`
			`ftp`
			`</server>`
Kill the server when this test is done, as other FTP-tests sometimes have problems otherwise. 2004-02-26 17:40:33 -05:00			`<killserver>`
			`ftp`
			`</killserver>`
new tests 2001-11-02 18:09:02 -05:00			`<name>`
			`FTP download with strict timeout and slow CWD`
			`</name>`
Add 'timeout' and 'delay' attributes support for the test harness <command> subsection 2008-04-25 00:19:50 -04:00			`<command timeout="1">`
1 - allow much longer time for the test FTP server to startup and get verified 2 - store the time it took to verify it and allow that time to be used as %FTPTIME[23] in command lines to allow us to adjust better to slow hosts since test 190 failed on my slow solaris machine just because it hadn't gotten time to run all the way the test assumed all machines would reach before the time-out elapsed. 2006-05-11 02:34:30 -04:00			`ftp://%HOSTIP:%FTPPORT/path/to/file/190 -m %FTPTIME2`
new tests 2001-11-02 18:09:02 -05:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
new tests 2001-11-02 18:09:02 -05:00
			`# Verify data after the test has been "shot"`
			`<verify>`
Renamed several libcurl error codes and options to make them more general and allow reuse by multiple protocols. Several unused error codes were removed. In all cases, macros were added to preserve source (and binary) compatibility with the old names. These macros are subject to removal at a future date, but probably not before 2009. An application can be tested to see if it is using any obsolete code by compiling it with the CURL_NO_OLDIES macro defined. Documented some newer error codes in libcurl-error(3) 2007-08-30 16:34:57 -04:00			`# 28 is CURLE_OPERATION_TIMEDOUT`
new tests 2001-11-02 18:09:02 -05:00			`<errorcode>`
			`28`
			`</errorcode>`
			`<protocol>`
			`USER anonymous`
ftp@example.com is now the new anonymous FTP password. I opted for 'ftp' on the left side of @ to make it short(er). 2007-02-13 17:50:16 -05:00			`PASS ftp@example.com`
new tests 2001-11-02 18:09:02 -05:00			`PWD`
modified to work with modified code 2003-04-30 13:16:25 -04:00			`CWD path`
new tests 2001-11-02 18:09:02 -05:00			`</protocol>`
			`</verify>`
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`</testcase>`