434 unit tests are starting to get a little unwieldy to run every time. It would be nice to be able to execute the unit tests by library using make. That way, I only have to run what I'm working on.
Maybe, some special rules to make check_sfl or make check_sfw. That might be difficult to implement and even more difficult to support. Maybe, the file comment blocks are enough. Maybe add a default comment on the pre-existing super secret make -C code dist/check_sfl_create_hard_link.bin command... but one that would build and run just test cases that match code/dist/check_sfl_*.bin.
Maybe, this isn't even a Makefile problem to solve. Maybe there's a way to wrap all these Check unit tests into some grand overarching structure like we've been doing on DCTHA for years. Python's unittest makes it real easy to "discover" test cases. Shouldn't there be something like that for Check?
434 unit tests are starting to get a little unwieldy to run every time. It would be nice to be able to execute the unit tests by library using
make
. That way, I only have to run what I'm working on.Maybe, some special rules to
make check_sfl
ormake check_sfw
. That might be difficult to implement and even more difficult to support. Maybe, the file comment blocks are enough. Maybe add a default comment on the pre-existing super secretmake -C code dist/check_sfl_create_hard_link.bin
command... but one that would build and run just test cases that matchcode/dist/check_sfl_*.bin
.Maybe, this isn't even a Makefile problem to solve. Maybe there's a way to wrap all these Check unit tests into some grand overarching structure like we've been doing on DCTHA for years. Python's
unittest
makes it real easy to "discover" test cases. Shouldn't there be something like that for Check?