zint-barcode-generator/frontend/tests
gitlost 93c3e27fba CODE128: Add minimal encodation algorithm (non-extended ASCII only)
from ZXing (props Alex Geller) - about 25-60% slower depending on
  data & stack heavy but does improve some outcomes when FNC1s
  present (GS1_MODE or manual) although not much else it appears
  (the previous algorithm was very good), but has a logical clarity
  the other lacked - funcs `c128_dxsmooth()` etc shared with
  CODE16K now moved there and renamed as `c16k_`;
  also fix extended char latching when exactly 4 extended chars
  at end
  also manual code set switching now honoured exactly even if
  immediate shift required;
manual: make explicit that AI "(00)" and "(01)" prefixes added by
  Zint are HRT-only
general: add `extern "C"` wrappers to a few header files
2024-09-07 12:44:16 +01:00
..
cmake/Modules Remove further refs to QZint; win32/README; add zintconfig.h to Win make files 2020-11-24 22:22:12 +00:00
CMakeLists.txt CMake: allow ctest to be run without having to install zint or 2023-01-09 01:14:42 +00:00
README - BMP/EMF/PCX/TIF: fix endianness on big-endian machines (note TIF 2024-01-17 01:45:45 +00:00
test_args.c CODE128: Add minimal encodation algorithm (non-extended ASCII only) 2024-09-07 12:44:16 +01:00

% 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.