comment on

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

prove -rlj6
[download]

from the project directory or

prove -rlj6 --formatter=TAP::Formatter::JUnit --timer t/| tee junit.xm
+l
[download]

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

#!/bin/sh
perl Makefile.PL
make
make test

# do something with newly created files

make veryclean
[download]

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. :)

jeffa

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)

In reply to Re: C test suite management with perl by jeffa
in thread C test suite management with perl by QuillMeantTen

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks