curl/tests/data/test1394

<testcase>
<info>
<keywords>
unittest
</keywords>
</info>

#
# Client-side
<client>
<server>
none
</server>
<features>
unittest
</features>
<name>
unit test for parse_cert_parameter()
</name>
<tool>
tool%TESTNUMBER
</tool>
</client>

<verify>
<stdout mode="text">
</stdout>
</verify>
</testcase>
unit1394.c: plug the curl tool unit test in 2013-05-03 13:26:25 +02:00			`<testcase>`
			`<info>`
			`<keywords>`
			`unittest`
			`</keywords>`
			`</info>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<features>`
			`unittest`
			`</features>`
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 11:35:54 +02:00			`<name>`
unit1394.c: plug the curl tool unit test in 2013-05-03 13:26:25 +02:00			`unit test for parse_cert_parameter()`
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 11:35:54 +02:00			`</name>`
tests/tunit: make a separate directory for tool-based unit tests Separated from library based unit tests to not confuse memory management etc. Move 1394 and 1604 there. Closes #16983 2025-04-05 22:42:09 +02:00			`<tool>`
			`tool%TESTNUMBER`
			`</tool>`
unit1394.c: plug the curl tool unit test in 2013-05-03 13:26:25 +02:00			`</client>`

			`<verify>`
			`<stdout mode="text">`
			`</stdout>`
			`</verify>`
			`</testcase>`