1
0
mirror of https://github.com/moparisthebest/curl synced 2024-12-24 17:18:48 -05:00
curl/tests/unit
Anders Bakken 50d1b3379a CURLOPT_RESOLVE: Add support for multiple IP addresses per entry
This enables users to preresolve but still take advantage of happy
eyeballs and trying multiple addresses if some are not connecting.

Ref: https://github.com/curl/curl/pull/2260
2018-02-20 04:24:28 -05:00
..
.gitignore tests/unit/.gitignore: hide unit1601 and above, too 2015-04-22 14:20:20 +02:00
CMakeLists.txt includes: remove curl/curlbuild.h and curl/curlrules.h 2017-06-14 11:07:33 +02:00
curlcheck.h tests: fix -Wcast-qual warnings 2017-05-05 21:29:50 +02:00
Makefile.am includes: remove curl/curlbuild.h and curl/curlrules.h 2017-06-14 11:07:33 +02:00
Makefile.inc CURLOPT_RESOLVE: Add support for multiple IP addresses per entry 2018-02-20 04:24:28 -05:00
README removed trailing whitespace 2011-12-30 03:36:18 +01:00
unit1300.c code style: use spaces around equals signs 2017-09-11 09:29:50 +02:00
unit1301.c unit1301: fix error message on first test 2017-08-31 11:37:13 +02:00
unit1302.c tests: Make sure libtests & unittests call curl_global_cleanup() 2017-08-26 22:01:42 +02:00
unit1303.c code style: use spaces around equals signs 2017-09-11 09:29:50 +02:00
unit1304.c checksrc: white space edits to comply to stricter checksrc 2016-11-24 23:58:22 +01:00
unit1305.c code style: use spaces around pluses 2017-09-11 09:29:50 +02:00
unit1307.c fnmatch: pattern syntax can no longer fail 2018-01-31 01:17:35 +01:00
unit1308.c mime: tests and examples. 2017-09-02 19:08:45 +01:00
unit1309.c code style: use spaces around pluses 2017-09-11 09:29:50 +02:00
unit1323.c timediff: return timediff_t from the time diff functions 2017-10-25 09:54:37 +02:00
unit1330.c URLs: change all http:// URLs to https:// 2016-02-03 00:19:02 +01:00
unit1394.c unit: make unit test source code checksrc compliant 2016-04-03 22:38:36 +02:00
unit1395.c code style: use spaces around equals signs 2017-09-11 09:29:50 +02:00
unit1396.c code style: use spaces around equals signs 2017-09-11 09:29:50 +02:00
unit1397.c code: style updates 2016-04-03 22:38:36 +02:00
unit1398.c code style: use spaces around equals signs 2017-09-11 09:29:50 +02:00
unit1399.c time: rename Curl_tvnow to Curl_now 2017-10-25 18:48:05 +02:00
unit1600.c tests: Make sure libtests & unittests call curl_global_cleanup() 2017-08-26 22:01:42 +02:00
unit1601.c unit: make unit test source code checksrc compliant 2016-04-03 22:38:36 +02:00
unit1602.c checksrc: white space edits to comply to stricter checksrc 2016-11-24 23:58:22 +01:00
unit1603.c code: style updates 2016-04-03 22:38:36 +02:00
unit1604.c docs/comments: Update to secure URL versions 2017-08-08 21:41:07 +02:00
unit1605.c tests: Make sure libtests & unittests call curl_global_cleanup() 2017-08-26 22:01:42 +02:00
unit1606.c unit1606: Fixed shadowed variable warning 2017-08-28 23:55:55 +02:00
unit1607.c CURLOPT_RESOLVE: Add support for multiple IP addresses per entry 2018-02-20 04:24:28 -05: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 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 -------------------------------