curl/tests/unit
Daniel Stenberg bdb2dbc103
urlapi: strip off scope id from numerical IPv6 addresses
... to make the host name "usable". Store the scope id and put it back
when extracting a URL out of it.

Also makes curl_url_set() syntax check CURLUPART_HOST.

Fixes #3817
Closes #3822
2019-05-03 12:17:22 +02:00
..
.gitignore
CMakeLists.txt
curlcheck.h
Makefile.am makefile: make checksrc and hugefile commands "silent" 2019-03-14 20:11:24 +01:00
Makefile.inc alt-svc: the libcurl bits 2019-03-03 11:17:52 +01:00
README
unit1300.c
unit1301.c
unit1302.c
unit1303.c
unit1304.c
unit1305.c
unit1307.c unit1307: just fail without FTP support 2019-02-15 09:50:52 +01:00
unit1308.c
unit1309.c
unit1323.c
unit1330.c
unit1394.c
unit1395.c
unit1396.c
unit1397.c
unit1398.c
unit1399.c
unit1600.c
unit1601.c
unit1602.c
unit1603.c
unit1604.c
unit1605.c
unit1606.c
unit1607.c CURLOPT_DNS_USE_GLOBAL_CACHE: remove 2019-04-11 22:22:39 +02:00
unit1608.c tests: Run global cleanup at end of tests 2019-04-15 15:23:58 +02:00
unit1609.c CURLOPT_DNS_USE_GLOBAL_CACHE: remove 2019-04-11 22:22:39 +02:00
unit1620.c
unit1621.c xattr: skip unittest on unsupported platforms 2019-04-11 09:22:22 +02:00
unit1650.c tests: fix multiple may be used uninitialized warnings 2019-03-05 14:38:25 +01:00
unit1651.c unit1651: survive curl_easy_init() fails 2019-02-19 09:08:28 +01:00
unit1652.c
unit1653.c urlapi: strip off scope id from numerical IPv6 addresses 2019-05-03 12:17:22 +02:00
unit1654.c alt-svc: the libcurl bits 2019-03-03 11:17:52 +01:00

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