curl-curl/tests/unit
Stefan Eissing 357808f4ad
multi: add notifications API
Add infrastructure to colled and dispatch notifications for transfers
and the multi handle in general. Applications can register a callback
and en-/disable notification type the are interested in.

Without a callback installed, notifications are not collected. Same when
a notification type has not been enabled.

Memory allocation failures on adding notifications lead to a general
multi failure state and result in CURLM_OUT_OF_MEMORY returned from
curl_multi_perform() and curl_multi_socket*() invocations.

Closes #18432
2025-10-07 10:55:31 +02:00
..
.gitignore tests: always make bundles, adapt build and tests 2025-06-14 21:08:23 +02:00
CMakeLists.txt build: tidy up compiler definition for tests 2025-07-28 12:43:01 +02:00
Makefile.am lib: stop overriding system printf symbols 2025-10-06 20:57:59 +02:00
Makefile.inc tests: move curlcheck.h to libtest as unitcheck.h 2025-07-09 02:29:25 +02:00
README.md tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1300.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1302.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1303.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1304.c tidy-up: whitespace 2025-09-15 15:00:11 +02:00
unit1305.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1307.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1309.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1323.c unit1323: sync time types and printf masks, drop casts 2025-10-06 03:27:57 +02:00
unit1330.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1395.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1396.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1397.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1398.c build: address some -Weverything warnings, update picky warnings 2025-09-20 10:16:15 +02:00
unit1399.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1600.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1601.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1602.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1603.c tidy-up: drop stray "unused" comments 2025-09-03 16:31:16 +02:00
unit1605.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1606.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1607.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1608.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1609.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1610.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1611.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1612.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1614.c noproxy: fix the IPV6 network mask pattern match 2025-10-06 23:49:31 +02:00
unit1615.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1616.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1620.c url: make Curl_init_userdefined return void 2025-10-05 22:58:20 +02:00
unit1650.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1651.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1652.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1653.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1654.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1655.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1656.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1657.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1658.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1660.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit1661.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1663.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1664.c unit1664: drop casts, expand masks to full values 2025-10-04 17:49:21 +02:00
unit1979.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit1980.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit2600.c lib: replace getsock() logic with pollsets 2025-08-04 23:43:13 +02:00
unit2601.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit2602.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit2603.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit2604.c tests: stop overriding system printf symbols 2025-10-04 00:51:06 +02:00
unit3200.c build: avoid overriding system symbols for fopen functions 2025-09-30 01:10:36 +02:00
unit3205.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit3211.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit3212.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit3213.c tests: constify command-line arguments 2025-07-29 13:44:50 +02:00
unit3214.c multi: add notifications API 2025-10-07 10:55:31 +02: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 is a separate static libcurl built that is 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 get told. The test case then has output left in the %LOGDIR 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 previously unused number.

Add your test to tests/unit/Makefile.inc (if it is a unit test). Add your test data filename to tests/data/Makefile.am

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.md documentation.

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

    #include "unitcheck.h"

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

    static CURLcode test_unit9998(const char *arg)
    {
      UNITTEST_BEGIN_SIMPLE

      /* 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_END_SIMPLE
    }

Here's an example using optional initialization and cleanup:

    #include "unitcheck.h"

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

    static CURLcode t9999_setup(void)
    {
      /* whatever you want done first */
      return CURLE_OK;
    }

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

    static CURLcode test_unit9999(const char *arg)
    {
      UNITTEST_BEGIN(t9999_setup())

      /* 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_END(t9999_stop())
    }