The mock that I created is a very simple C program that would need to be compiled before running the tests using a Makefile already available.

There might be an easier way... but if all else fails, you can always add an extra target (which builds you C program) to the generated Makefile and add it as a prerequisite to the test target, so that your program would be built right before testing.

Something like this (assuming you have your C stuff in a subdirectory mymock, and that mymock/Makefile would build the target executable mymock/mymock): 

### Makefile.PL

WriteMakefile(
    ...
);

package MY;

# override / modify test target
sub test {
    my $t = shift->SUPER::test(@_);
    $t =~ s|^test ::\K| mymock/mymock |m;  # inserts your prereq
    return $t;
}

# add your own target
sub postamble {
    return <<'MAKE_MOCK';
mymock/mymock : mymock/Makefile
    cd mymock && $(MAKE) all

MAKE_MOCK
}

[download]

(untested)

See also Overriding MakeMaker Methods.

Portability might well be an issue here, so you might ultimately be better off implementing your mock program in pure Perl... (if that's possible)

In reply to Re: CPAN automated tests for IPC by Eliya
in thread CPAN automated tests for IPC by glasswalk3r

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.