mirrors/zint-barcode-generator
1
0
Fork 0
mirror of https://git.code.sf.net/p/zint/code synced 2024-09-19 15:28:56 -04:00
Code Issues Projects Releases Packages Wiki Activity
zint-barcode-generator/frontend/tests
History
gitlost 9ae4e347d7 CLI: return ZINT_ERROR_INVALID_OPTION instead of 1 on bad option and 
ZINT_WARN_INVALID_OPTION instead of 0 on ignored option;
  more barcode synonyms
manual: append man page zint.1.pmd instead of CLI help;
  various tweaks and fiddlings;
  rMQR add ISO 23941 (released the other day but haven't got yet)
man page: expand and tweak
doc/Makefile: add HTML demo
2022-05-22 21:33:45 +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 CMakeLists.txt: cmake min required 3.13 -> 3.5 using CMAKE_REQUIRED_LIBRARIES; add ZINT_COVERAGE option 2021-07-26 15:29:05 +01:00
README CODEONE/DATAMATRIX/MAILMARK/PLESSEY: fix some 32-bit/portability bugs 2021-06-10 11:15:39 +01:00
test_args.c CLI: return ZINT_ERROR_INVALID_OPTION instead of 1 on bad option and 2022-05-22 21:33:45 +01:00

README 

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.