|Don't ask to ask, just ask|
Re: C test suite management with perlby jeffa (Bishop)
|on Sep 09, 2015 at 17:39 UTC||Need Help??|
Why not just use prove? If you just want to run your tests, and you don' t care about the order they are run in (and you should not to take advantage of forked parallelization) then prove will handle pretty much everything your run_tests.pl script does.
I put all my tests into a directory named t/ inside the project directory and run
from the project directory or
if i want to feed the results to a CI server like Jenkins, so it can build pretty graphs for me.
If you want to build an executable then perhaps you can leverage Makefile.pl instead of rolling your own wheel from complete scratch. I recommend Module::Starter to start any and all projects. Once you have a proper Makefile.pl, then you can use the shell to replace build.pl
If you need more control, then i suggest starting with a foundation like App::Prove.
Hope this helps, there are many branches to hit when falling down this tree. :)
L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)