curl/tests/unit
Yang Tse 9f390a356e unit tests: build adjustment
Also define UNITTESTS macro when building unit test sources.

Fixing compiler warning: external definition with no prior declaration
2011-05-25 20:24:03 +02:00
..
.gitignore ignore: all executable unit test cases 2011-01-04 16:51:41 +01:00
Makefile.am unit tests: build adjustment 2011-05-25 20:24:03 +02:00
Makefile.inc unit tests: build adjustment 2011-05-25 20:24:03 +02:00
README unit tests: README, adjust header inclusion order 2011-05-24 21:23:52 +02:00
curlcheck.h sources: update source headers 2011-03-10 12:04:33 +01:00
unit1300.c compiler warning: fix 2011-05-24 17:35:08 +02:00
unit1301.c unit tests: adjust header inclusion order 2011-05-21 13:22:11 +02:00
unit1302.c unit tests: adjust header inclusion order 2011-05-21 13:22:11 +02:00
unit1303.c compiler warning: fix 2011-05-21 14:39:42 +02:00
unit1304.c compiler warning: fix 2011-05-24 17:35:08 +02:00
unit1305.c unit tests: adjust header inclusion order 2011-05-21 13:22:11 +02:00
unit1307.c unit tests: adjust header inclusion order 2011-05-21 13:22:11 +02:00

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 -------------------------------