mirror of
https://git.code.sf.net/p/zint/code
synced 2026-05-05 21:55:31 +00:00
3c193d7306
allow for heights smaller than `textoffset` when have add-on (buffer overflow for raster, outside vector height for vector) raster: EAN/UPC: make sure don't overwrite add-on stuff when line-copying guard descenders by limiting copy width ZBarcode_Encode_Segs: allow for multiple (stacked) rows when setting absolute minimum height; state stacked symbols max in error message DBAR_EXP: check length on encoding method 6 before trying to parse 3-digit currency string with `z_to_int()` CLI: stop looping over data args when have error; suppress taint warning by using fixed `malloc()` size for `arg_opts` instead of `argc` general: use `vsnprintf()` instead of `vsprintf()` if not C89 ULTRACODE: don't call `ult_generate_codewords()` if `length` 0 from fragment processing (avoids `assert()`) clang-tidy -> 23 & suppress some warnings test suite: fuzz: leave Z_FUZZ_DEBUG to compiler, fix comment general: some minor code-formatting on touched files README.deb -> README.debian (avoid confusion with actual ".deb") BWIPP: update to latest
% frontend/tests/README 2024-01-12
Zint frontend test suite
------------------------
See <project-dir>/backend/tests/README to see how to build the test suite.
In addition to the setup for the backend tests, the environment needs to be
able to find the `zint` application using that name. In UNIX-like systems
this can be configured by prepending the PATH variable with the frontend's
directory inside the build directory:
cd <build-dir>
export PATH=$(pwd)/frontend:${PATH}
------------------------------------------------------------------------------
the frontend test will be automatically run by cmake's ctest, however manual
invocation is also possible:
cd <build-dir>/frontend/test
./test_args
As with the backend tests, individual test functions and single dataset items
can be run using '-f <func-name>' and '-i <index>' etc.