mc/tests
Yury V. Zaytsev 877ef7d78b tests: don't free after ck_abort_msg as it's marked no-return
Signed-off-by: Yury V. Zaytsev <yury@shurup.com>
2024-10-19 08:56:56 +02:00
..
lib tests: don't free after ck_abort_msg as it's marked no-return 2024-10-19 08:56:56 +02:00
src Ticket #4584: re-implement mocking via weak symbols instead of symbol duplication 2024-10-19 08:56:40 +02:00
.gitignore tests: add .gitignore 2019-09-01 20:13:52 +03:00
Makefile.am Ticket #3708: fix usability problems with --enable-tests 2016-12-27 16:46:38 +04:00
mctest.h Indentation using GNU indent-2.2.13. 2024-06-02 12:49:13 +03:00
README Ticket #3708: fix usability problems with --enable-tests 2016-12-27 16:46:38 +04:00

Overview
--------

This tree contains unit tests.

To compile and run the tests, do 'make check' (either in the top folder,
or just in the folder containing the tests you're interested in).

IMPORTANT: To compile the tests, you need to have the "Check" unit
testing framework[1] installed.[2] If you have it installed, you will see
"Unit tests: yes" in configure's summary message; if you don't see this
message, you won't be able to compile the tests.[3]

Tips and tricks
---------------

* To be able to step with the debugger into test code, see [4]. E.g., do:

    $ export CK_FORK=no

[1]: http://libcheck.github.io/check/
[2]: Your package manager likely has it.
[3]: Actually, some tests (like src/vfs/extfs/helpers-list) don't use
     this framework and will compile just fine. But that's the exception.
[4]: http://stackoverflow.com/questions/1649814/debugging-unit-test-in-c-using-check