curl/tests/data/test628

<testcase>
<info>
<keywords>
SFTP
FAILURE
</keywords>
</info>

#
# Client-side
<client>
<server>
sftp
</server>
 <name>
SFTP invalid user login (password authentication)
 </name>
 <command>
-u not-a-valid-user: sftp://%HOSTIP:%SSHPORT%POSIX_PWD/irrelevant-file  --insecure
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
67
</errorcode>
<valgrind>
disable
</valgrind>
</verify>
</testcase>
Added SSH failure test cases 628-632 2008-06-19 00:18:58 +00:00			`<testcase>`
			`<info>`
			`<keywords>`
			`SFTP`
			`FAILURE`
			`</keywords>`
			`</info>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`sftp`
			`</server>`
			`<name>`
			`SFTP invalid user login (password authentication)`
			`</name>`
			`<command>`
Don't use Windows path %PWD for SSH tests All these tests failed on Windows because something like sftp://%HOSTIP:%SSHPORT%PWD/ expanded to sftp://127.0.0.1:1234c:/msys64/home/bla/curl and then curl complained about the port number ending with a letter. Use the original POSIX path instead of the Windows path created in checksystem to fix this. Closes https://github.com/curl/curl/pull/2920 2018-08-30 08:35:21 +02:00			`-u not-a-valid-user: sftp://%HOSTIP:%SSHPORT%POSIX_PWD/irrelevant-file --insecure`
Added SSH failure test cases 628-632 2008-06-19 00:18:58 +00:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`67`
			`</errorcode>`
			`<valgrind>`
			`disable`
			`</valgrind>`
			`</verify>`
			`</testcase>`