Mercurial > hgrepos > Python2 > PyMuPDF
comparison mupdf-source/thirdparty/zint/frontend/tests/README @ 3:2c135c81b16c
MERGE: upstream PyMuPDF 1.26.4 with MuPDF 1.26.7
| author | Franz Glasner <fzglas.hg@dom66.de> |
|---|---|
| date | Mon, 15 Sep 2025 11:44:09 +0200 |
| parents | b50eed0cc0ef |
| children |
comparison
equal
deleted
inserted
replaced
| 0:6015a75abc2d | 3:2c135c81b16c |
|---|---|
| 1 % frontend/tests/README 2024-01-12 | |
| 2 | |
| 3 Zint frontend test suite | |
| 4 ------------------------ | |
| 5 | |
| 6 See <project-dir>/backend/tests/README to see how to build the test suite. | |
| 7 In addition to the setup for the backend tests, the environment needs to be | |
| 8 able to find the `zint` application using that name. In UNIX-like systems | |
| 9 this can be configured by prepending the PATH variable with the frontend's | |
| 10 directory inside the build directory: | |
| 11 | |
| 12 cd <build-dir> | |
| 13 export PATH=$(pwd)/frontend:${PATH} | |
| 14 | |
| 15 | |
| 16 ------------------------------------------------------------------------------ | |
| 17 the frontend test will be automatically run by cmake's ctest, however manual | |
| 18 invocation is also possible: | |
| 19 | |
| 20 cd <build-dir>/frontend/test | |
| 21 ./test_args | |
| 22 | |
| 23 As with the backend tests, individual test functions and single dataset items | |
| 24 can be run using '-f <func-name>' and '-i <index>' etc. |