curl/tests/unit
Steve Holme c92c30edbd base64: Extended validation to look for invalid characters
Extended the basic validation in commit e17c1b25bc to return a
failure when invalid base64 characters are included.
2013-12-01 11:12:23 +00:00
..
.gitignore ignore: all executable unit test cases 2011-01-04 16:51:41 +01:00
Makefile.am src/Makefile.am: build static lib for unit tests if enabled 2013-05-06 15:03:12 +02:00
Makefile.inc dotdot: introducing dot file path cleanup 2013-06-22 14:15:07 +02:00
README removed trailing whitespace 2011-12-30 03:36:18 +01:00
curlcheck.h fix a bunch of MSVC compiler warnings 2011-09-03 16:07:09 +02:00
unit1300.c Revert changes relative to lib/*.[ch] recent renaming 2013-01-06 18:20:27 +01:00
unit1301.c Revert changes relative to lib/*.[ch] recent renaming 2013-01-06 18:20:27 +01:00
unit1302.c base64: Extended validation to look for invalid characters 2013-12-01 11:12:23 +00:00
unit1303.c Revert changes relative to lib/*.[ch] recent renaming 2013-01-06 18:20:27 +01:00
unit1304.c unit1304: include memdebug and free everything correctly 2013-08-29 12:50:15 +02:00
unit1305.c Revert changes relative to lib/*.[ch] recent renaming 2013-01-06 18:20:27 +01:00
unit1307.c unit tests: adjust header inclusion order 2011-05-21 13:22:11 +02:00
unit1308.c curl_formget: fix FILE * leak 2011-06-13 22:32:00 +02:00
unit1309.c Revert changes relative to lib/*.[ch] recent renaming 2013-01-06 18:20:27 +01:00
unit1330.c unit1330.c: fix date 2013-03-15 20:05:03 +01:00
unit1394.c unit1394.c: plug the curl tool unit test in 2013-05-06 15:03:13 +02:00
unit1395.c dotdot: introducing dot file path cleanup 2013-06-22 14:15:07 +02:00
unit1396.c unit1396: unit tests to verify curl_easy_(un)escape 2013-06-22 11:21:35 +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 -------------------------------