I have tests which I need to run in a custom way, and I'd like to be able to benefit from libtest-mimic's work to precisely emulate the standard test harness interface, but the most I can use, it seems, is using the public Arguments struct to parse arguments — there's no way to use the filtering implementation but not the runner.
Could you add a function which takes an Arguments and a set of test descriptions (like run()), and returns an iterator of which tests should be run, instead of running them? (Or in the case of --list, it would do the expected printing and return a value indicating to just exit.)
(It is of course already possible to insert placeholders as the individual test functions, but that would require each placeholder function to access global state for the real test harness, and to block until the test actually runs in order to report success/failure, which seems inelegant and potentially problematic.)
I have tests which I need to run in a custom way, and I'd like to be able to benefit from
libtest-mimic's work to precisely emulate the standard test harness interface, but the most I can use, it seems, is using the publicArgumentsstruct to parse arguments — there's no way to use the filtering implementation but not the runner.Could you add a function which takes an
Argumentsand a set of test descriptions (likerun()), and returns an iterator of which tests should be run, instead of running them? (Or in the case of--list, it would do the expected printing and return a value indicating to just exit.)(It is of course already possible to insert placeholders as the individual test functions, but that would require each placeholder function to access global state for the real test harness, and to block until the test actually runs in order to report success/failure, which seems inelegant and potentially problematic.)