Files
Andrew Borodin 2893ee212f Add tests for edit_replace_cmd().
* (status_msg_init): add MC_MOCKABLE attribute.
  * (status_msg_deinit): likewise.
  * (edit_search_update_callback): likewise.
  * (edit_dialog_replace_show): add MC_MOCKABLE and make public.
  * (edit_dialog_replace_prompt_show): likewise.
  * (edit_search_options): make public.
  * (B_REPLACE_ALL, B_REPLACE_ONE, B_SKIP_REPLACE): likewise.
  * (macros_list): init explicitly.
  * tests/src/editor/mc.charsets: add ASCII charset.
  * tests/src/editor/edit_replace_cmd.c: new file.
  * tests/src/editor/Makefile.am: add new test.

Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
2025-02-23 18:52:47 +03:00
..
2025-02-23 18:52:47 +03:00
2019-09-01 20:13:52 +03:00
2025-02-02 19:38:47 +01: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]: https://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]: https://stackoverflow.com/questions/1649814/debugging-unit-test-in-c-using-check