romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-04-18 11:51:41 +03:00
Code Issues Projects Releases Packages Wiki Activity
curl/tests/tunit
History
Viktor Szakats ee06673296
build: sync tests unity builds between cmake and autotools 
Instead of relying on CMake's built-in unity feature, use `mk-unity.pl`,
as already done with autotools. It simplified the build, shortens logs
and makes debugging easier because of the fewer build variations.
It also allows testing / fixing with cmake and those automatically apply
to autotools builds too. cmake builds can be much-much faster, esp.
when working the builds themselves.

It also enables "unity" in old cmake versions. Basically every test
target is a single generated .c source.

Also:
- drop a `lib` unity workaround for libtests with autotools after fixing
  the issue in libtests itself. It drops a few exceptions and makes
  libcurl build faster (in autotools unity).
- fix another `lib` autotools unity issue and drop the workaround for it
  from `mk-unity.pl`. `srcdir` was missing from the header path.
- simplify `mk-unity.pl` command-lines, drop exclusions.

Follow-up to 2c27a67daa #17590

Closes #17628
2025-06-16 01:07:41 +02:00
..
.gitignore tests: always make bundles, adapt build and tests 2025-06-14 21:08:23 +02:00
CMakeLists.txt build: sync tests unity builds between cmake and autotools 2025-06-16 01:07:41 +02:00
Makefile.am tests: always make bundles, adapt build and tests 2025-06-14 21:08:23 +02:00
Makefile.inc tests: always make bundles, adapt build and tests 2025-06-14 21:08:23 +02:00
README.md tests/tunit: make a separate directory for tool-based unit tests 2025-04-08 08:08:05 +02:00
tool1394.c tests: always make bundles, adapt build and tests 2025-06-14 21:08:23 +02:00
tool1604.c tests: always make bundles, adapt build and tests 2025-06-14 21:08:23 +02:00
tool1621.c tests: always make bundles, adapt build and tests 2025-06-14 21:08:23 +02:00

README.md

Tool unit tests

This directory is for unit testing of tool functions. They are separate from libcurl unit tests, because how these live/work outside of the library and the libcurl unit tests live/work inside.