What is the canonical way to run tests that take command line parameters?

[kavika13]

I'm writing a wrapper for this library, for use in a different programming language. I want to port over the tests as well, to improve my confidence that the wrapper is working correctly.

The unit tests seem to be small binary programs (with a main(argc, argv) and everything).
The instructions for the unit tests just seem to be instructions to compile and run an example test case.

The instructions:
https://github.com/mackron/miniaudio/blob/master/tests/_build/README.md

Some of the unit tests I found seem to require a command line parameter.
I am not finding anywhere in the repo any sort of canonical list of which parameters should be passed to those tests.

For example:
https://github.com/mackron/miniaudio/blob/master/tests/test_filtering/ma_test_filtering_dithering.c

It has the lines:

    if (argc < 2) {
        printf("No input file.\n");
        return -1;
    }

But I can't find a script that compiles and runs this particular test program.

I can find a higher level test that includes and runs all the filtering subtests, but it seems to just register those subtests and pass its own command line arguments to them. And I can't find a script that calls that higher level test, to see which command line parameters are supposed to be passed to it.

The higher level test:
https://github.com/mackron/miniaudio/blob/master/tests/test_filtering/ma_test_filtering.c

Any idea where to find an existing higher order script that actually runs all of these? Or are these tests sort of unused at this point?

[mackron]

The tests are very casual. I built them mainly just for my own testing during development. There's no script of anything to automatically compile and run the test programs. I just run them myself manually one by one as needed. Also, some tests like the deviceio test require active listening so you won't be able to automate them.