The test runner script now knows if unittests can run and the unit test
setup file says it is one. I also made runtests.pl deal with no
<command> tag set, so that the description file can get even simpler.
OpenSSL
SSL
socks
+unittest
as well as each protocol that curl supports. A protocol only needs to be
specified if it is different from the server (useful when the server
<tool>
Name of tool to use instead of "curl". This tool must be built and exist
-in the libtest/ directory.
+either in the libtest/ directory (if the tool starts with 'lib') or in the
+unit/ directory (if the tool starts with 'unit').
</tool>
<name>
<info>
<keywords>
unittest
+llist
</keywords>
</info>
<server>
none
</server>
+<features>
+unittest
+</features>
<name>
llist unit tests
</name>
<tool>
unit1300
</tool>
-<command>
-unit1300
-</command>
</client>
-#
-# Verify data after the test has been "shot"
-<verify>
-
-</verify>
</testcase>
next;
}
}
+ elsif($f eq "unittest") {
+ if($debug_build) {
+ next;
+ }
+ }
elsif($f eq "large_file") {
if($large_file) {
next;
# substitute variables in the command line
subVariables \$cmd;
}
+ else {
+ # there was no command given, use something silly
+ $cmd="-";
+ }
if($curl_debug) {
unlink($memdump);
}