curl/tests/unit
Viktor Szakats 2a292c3984
build: add Windows CE / CeGCC support, with CI jobs
Make it possible to build curl for Windows CE using the CeGCC toolchain.
With both CMake and autotools, including tests and examples, also in CI.
The build configuration is the default one with Schannel enabled. No
3rd-party dependencies have been tested.

Also revive old code to make Schannel build with Windows CE, including
certificate verification.

Builds have been throughougly tested. But, I've made no functional tests
for this PR. Some parts (esp. file operations, like truncate and seek)
are stubbed out and likely broken as a result. Test servers build, but
they do not work on Windows CE. This patch substitutes `fstat()` calls
with `stat()`, which operate on filenames, not file handles. This may or
may not work and/or may not be secure.

About CeGCC: I used the latest available macOS binary build v0.59.1
r1397 from 2009, in native `mingw32ce` build mode. CeGCC is in effect
MinGW + GCC 4.4.0 + old/classic-mingw Windows headers. It targets
Windows CE v3.0 according to its `_WIN32_WCE` value. It means this PR
restores portions of old/classic-mingw support. It makes the Windows CE
codepath compatible with GCC 4.4.0. It also adds workaround for CMake,
which cannot identify and configure this toolchain out of the box.

Notes:
- CMake doesn't recognize CeGCC/mingw32ce, necessitating tricks as seen
  with Amiga and MS-DOS.
- CMake doesn't set `MINGW` for mingw32ce. Set it and `MINGW32CE`
  manually as a helper variable, in addition to `WINCE` which CMake sets
  based on `CMAKE_SYSTEM_NAME`.
- CMake fails to create an implib for `libcurl.dll`, due to not
  recognizing the platform as a Windowsy one. This patch adds the
  necessary workaround to make it work.
- headers shipping with CeGCC miss some things curl needs for Schannel
  support. Fixed by restoring and renovating code previously deleted
  old-mingw code.
- it's sometime non-trivial to figure out if a fallout is WinCE,
  mingw32ce, old-mingw, or GCC version-specific.
- WinCE is always Unicode. With exceptions: no `wmain`,
  `GetProcAddress()`.
- `_fileno()` is said to convert from `FILE *` to `void *` which is
  a Win32 file `HANDLE`. (This patch doesn't use this, but with further
  effort it probably could be.)
  https://stackoverflow.com/questions/3989545/how-do-i-get-the-file-handle-from-the-fopen-file-structure
- WinCE has no signals, current directory, stdio/CRT file handles, no
  `_get_osfhandle()`, no `errno`, no `errno.h`. Some of this stuff is
  standard C89, yet missing from this platform. Microsoft expects
  Windows CE apps to use Win32 file API and `FILE *` exclusively.
- revived CeGCC here (not tested for this PR):
  https://building.enlyze.com/posts/a-new-windows-ce-x86-compiler-in-2024/

On `UNDER_CE` vs. `_WIN32_WCE`: (This patch settled on `UNDER_CE`)

- A custom VS2008 WinCE toolchain does not set any of these.
  The compiler binaries don't contain these strings, and has no compiler
  option for targeting WinCE, hinting that a vanilla toolchain isn't
  setting any of them either.
- `UNDER_CE` is automatically defined by the CeGCC compiler.
  https://cegcc.sourceforge.net/docs/details.html
- `UNDER_CE` is similar to `_WIN32`, except it's not set automatically
  by all compilers. It's not supposed to have any value, like a version.
  (Though e.g. OpenSSL sets it to a version)
- `_WIN32_WCE` is the CE counterpart of the non-CE `_WIN32_WINNT` macro.
  That does return the targeted Windows CE version.
- `_WIN32_WCE` is not defined by compilers, and relies on a header
  setting it to a default, or the build to set it to the desired target
  version. This is also how `_WIN32_WINNT` works.
- `_WIN32_WCE` default is set by `windef.h` in CeGCC.
- `_WIN32_WCE` isn't set to a default by MSVC Windows CE headers (the
  ones I checked at least).
- CMake sets `_WIN32_WCE=<ver>`, `UNDER_CE`, `WINCE` for MSVC WinCE.
- `_WIN32_WCE` seems more popular in other projects, including CeGCC
  itself. `zlib` is a notable exception amongst curl dependencies,
  which uses `UNDER_CE`.
- Since `_WIN32_WCE` needs "certain" headers to have it defined, it's
  undefined depending on headers included beforehand.
- `curl/curl.h` re-uses `_WIN32_WCE`'s as a self-guard, relying on
  its not-(necessarily)-defined-by-default property:
  25b445e479/include/curl/curl.h (L77)

Toolchain downloads:
- Windows:
  https://downloads.sourceforge.net/cegcc/cegcc/0.59.1/cegcc_mingw32ce_cygwin1.7_r1399.tar.bz2
- macOS Intel:
  https://downloads.sourceforge.net/cegcc/cegcc/0.59.1/cegcc_mingw32ce_snowleopard_r1397.tar.bz2

Closes #15975
2025-02-21 13:56:34 +01:00
..
.gitignore tidy-up: .gitignore lines mostly 2025-01-27 20:59:46 +01:00
CMakeLists.txt cmake: namespace functions and macros 2024-12-16 21:55:00 +01:00
curlcheck.h Makefile.mk: drop in favour of autotools and cmake (MS-DOS, AmigaOS3) 2024-12-16 23:20:55 +01:00
Makefile.am checksrc: exclude generated bundle files to avoid race condition 2025-01-27 20:59:47 +01:00
Makefile.inc x509asn1: add parse recursion limit 2025-02-03 20:10:09 +01:00
README.md docs: use lowercase curl and libcurl 2025-01-02 17:15:54 +01:00
unit1300.c unit1300: fix checksrc longline warnings 2024-08-21 03:37:29 -04:00
unit1302.c tests: speed up builds with single-binary test bundles 2024-09-22 09:51:15 +02:00
unit1303.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1304.c netrc: address several netrc parser flaws 2024-11-17 11:33:56 +01:00
unit1305.c tests: speed up builds with single-binary test bundles 2024-09-22 09:51:15 +02:00
unit1307.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1308.c build: tidy up deprecation suppression, enable warnings for clang 2024-09-21 00:59:52 +02:00
unit1309.c lib/src: white space edits to comply better with code style 2024-09-19 14:59:12 +02:00
unit1323.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1330.c
unit1394.c
unit1395.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1396.c
unit1397.c
unit1398.c build: fix compiling with GCC 4.x versions 2025-01-22 11:26:15 +01:00
unit1399.c lib/src: white space edits to comply better with code style 2024-09-19 14:59:12 +02:00
unit1600.c
unit1601.c
unit1602.c src: fix potential macro confusion in cmake unity builds 2024-08-22 10:45:04 +02:00
unit1603.c src: fix potential macro confusion in cmake unity builds 2024-08-22 10:45:04 +02:00
unit1604.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1605.c
unit1606.c tests: speed up builds with single-binary test bundles 2024-09-22 09:51:15 +02:00
unit1607.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1608.c
unit1609.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1610.c lib: prefer CURL_SHA256_DIGEST_LENGTH over the unprefixed name 2024-08-13 10:04:06 +02:00
unit1611.c
unit1612.c lib: remove function pointer typecasts for hmac/sha256/md5 2024-10-15 14:32:39 +02:00
unit1614.c CI: move Azure jobs to GHA, fix fallouts, sshserver, runtests tweaks 2024-09-16 10:00:17 +02:00
unit1615.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1616.c src: fix potential macro confusion in cmake unity builds 2024-08-22 10:45:04 +02:00
unit1620.c tests: extend user/password parsing test1620 2024-05-25 23:48:57 +02:00
unit1621.c
unit1650.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1651.c build: fix some -Wsign-conversion/-Warith-conversion warnings 2023-12-19 12:45:28 +00:00
unit1652.c build: fix compiling with GCC 4.x versions 2025-01-22 11:26:15 +01:00
unit1653.c
unit1654.c llist: remove direct struct accesses, use only functions 2024-08-12 13:18:10 +02:00
unit1655.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1656.c tidy-up: make per-file ARRAYSIZE macros global as CURL_ARRAYSIZE 2025-02-07 14:21:59 +01:00
unit1657.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +01:00
unit1660.c strparse: string parsing helper functions 2024-12-12 16:00:52 +01:00
unit1661.c tests: libtests and unit tests need explicit #include memdebug 2024-09-22 21:25:31 +02:00
unit1663.c tests: speed up builds with single-binary test bundles 2024-09-22 09:51:15 +02:00
unit1664.c strparse: speed up the hex parser somewhat 2025-02-19 07:49:06 +01:00
unit2600.c build: add Windows CE / CeGCC support, with CI jobs 2025-02-21 13:56:34 +01:00
unit2601.c bufq: unwrite fix 2024-10-03 13:27:36 +02:00
unit2602.c
unit2603.c CI: move Azure jobs to GHA, fix fallouts, sshserver, runtests tweaks 2024-09-16 10:00:17 +02:00
unit2604.c build: fix compiling with GCC 4.x versions 2025-01-22 11:26:15 +01:00
unit3200.c build: fix compiling with GCC 4.x versions 2025-01-22 11:26:15 +01:00
unit3205.c tidy-up: use CURL_ARRAYSIZE() 2025-02-19 00:59:45 +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 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 "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