Dan Fandrich 7cb763cf57 test1397: Fixed compilation with some SSL backends 10 anni fa
..
.gitignore 1e52ea92eb ignore: all executable unit test cases 14 anni fa
Makefile.am 683f2b8323 src/Makefile.am: build static lib for unit tests if enabled 11 anni fa
Makefile.inc 4d06b27921 test1397: unit test for certificate name wildcard handling 10 anni fa
README ed0364343d removed trailing whitespace 13 anni fa
curlcheck.h 6b75d2c2df fix a bunch of MSVC compiler warnings 13 anni fa
unit1300.c 4a5aa6682d Revert changes relative to lib/*.[ch] recent renaming 12 anni fa
unit1301.c 4a5aa6682d Revert changes relative to lib/*.[ch] recent renaming 12 anni fa
unit1302.c c92c30edbd base64: Extended validation to look for invalid characters 11 anni fa
unit1303.c 4a5aa6682d Revert changes relative to lib/*.[ch] recent renaming 12 anni fa
unit1304.c f00899d73e unit1304: make the test pass the OOM torture tests 10 anni fa
unit1305.c d28b70d152 unittests: do not include curl_memory.h 11 anni fa
unit1307.c 02f3ff3b0a unit tests: adjust header inclusion order 13 anni fa
unit1308.c 0aedccc18a curl_formget: fix FILE * leak 13 anni fa
unit1309.c 4a5aa6682d Revert changes relative to lib/*.[ch] recent renaming 12 anni fa
unit1330.c 8ce915c7a4 unit1330.c: fix date 11 anni fa
unit1394.c d28b70d152 unittests: do not include curl_memory.h 11 anni fa
unit1395.c 7877619f85 dotdot: introducing dot file path cleanup 11 anni fa
unit1396.c 00b1e52823 unit1396: make the test pass the OOM torture tests 10 anni fa
unit1397.c 7cb763cf57 test1397: Fixed compilation with some SSL backends 10 anni fa

README

Unit tests
==========

The goal is to add tests for *ALL* functions in libcurl. If functions are too
big and complicated, we should split them into smaller and testable ones.

Build Unit Tests
================

'./configure --enable-debug' is required for the unit tests to build. To
enable unit tests, there will be a separate static libcurl built that will be
used exclusively for linking unit test programs. Just build everything as
normal, and then you can run the unit test cases as well.

Run Unit Tests
==============

Unit tests are run as part of the regular test suite. If you have built
everything to run unit tests, to can do 'make test' at the root level. Or you
can 'cd tests' and then invoke individual unit tests with ./runtests.pl NNNN
where NNNN is the specific test number.

Debug Unit Tests
================

If a specific test fails you will get told. The test case then has output left
in the log/ subdirectory, but most importantly you can re-run the test again
using gdb by doing ./runtests.pl -g NNNN. That is, add a -g to make it start
up gdb and run the same case using that.

Write Unit Tests
================

We put tests that focus on an area or a specific function into a single C
source file. The source file should be named 'unitNNNN.c' where NNNN is a
number that starts with 1300 and you can pick the next free number.

You also need a separate file called tests/data/testNNNN (using the same
number) that describes your test case. See the test1300 file for inspiration
and the tests/FILEFORMAT documentation.

For the actual C file, here's a very simple example:

----------------------- start -------------------------------
#include "curlcheck.h"

#include "a libcurl header.h" /* from the lib dir */

static void unit_setup( void )
{
/* whatever you want done first */
}

static void unit_stop( void )
{
/* done before shutting down and exiting */
}

UNITTEST_START

/* here you start doing things and checking that the results are good */

fail_unless( size == 0 , "initial size should be zero" );
fail_if( head == NULL , "head should not be initiated to NULL" );

/* you end the test code like this: */

UNITTEST_STOP

----------------------- end -------------------------------