curl/tests/unit
Viktor Szakats 2dbe75bd7f
build: fix some -Wsign-conversion/-Warith-conversion warnings
- enable `-Wsign-conversion` warnings, but also setting them to not
  raise errors.
- fix `-Warith-conversion` warnings seen in CI.
  These are triggered by `-Wsign-converion` and causing errors unless
  explicitly silenced. It makes more sense to fix them, there just a few
  of them.
- fix some `-Wsign-conversion` warnings.
- hide `-Wsign-conversion` warnings with a `#pragma`.
- add macro `CURL_WARN_SIGN_CONVERSION` to unhide them on a per-build
  basis.
- update a CI job to unhide them with the above macro:
  https://github.com/curl/curl/actions/workflows/linux.yml -> OpenSSL -O3

Closes #12492
2023-12-19 12:45:28 +00:00
..
.gitignore
CMakeLists.txt
curlcheck.h build: add more picky warnings and fix them 2023-11-21 16:35:42 +00:00
Makefile.am
Makefile.inc
README.md
unit1300.c
unit1302.c
unit1303.c
unit1304.c
unit1305.c
unit1307.c
unit1308.c
unit1309.c
unit1323.c
unit1330.c
unit1394.c windows: use built-in _WIN32 macro to detect Windows 2023-11-22 15:42:25 +00:00
unit1395.c autotools: stop setting -std=gnu89 with --enable-warnings 2023-11-20 22:28:17 +00:00
unit1396.c
unit1397.c
unit1398.c
unit1399.c
unit1600.c
unit1601.c
unit1602.c
unit1603.c
unit1604.c windows: use built-in _WIN32 macro to detect Windows 2023-11-22 15:42:25 +00:00
unit1605.c
unit1606.c
unit1607.c
unit1608.c
unit1609.c
unit1610.c
unit1611.c
unit1612.c
unit1614.c
unit1620.c
unit1621.c
unit1650.c
unit1651.c build: fix some -Wsign-conversion/-Warith-conversion warnings 2023-12-19 12:45:28 +00:00
unit1652.c build: enable missing OpenSSF-recommended warnings, with fixes 2023-12-16 13:12:37 +00:00
unit1653.c
unit1654.c
unit1655.c
unit1660.c
unit1661.c
unit2600.c misc: fix -Walloc-size warnings 2023-11-11 23:35:47 +01:00
unit2601.c
unit2602.c
unit2603.c
unit3200.c build: always revert #pragma GCC diagnostic after use 2023-11-18 11:16:32 +00: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 %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 file name to tests/data/Makefile.inc

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 "curlcheck.h"

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

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

    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