Yeah, but it is also quite easy to implement a Test::More like testsuite in C with libtab (http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap). This library is pretty small, so you can ship it with your program. I just added a 't' directory in my autoconf based project and put the libtab header and sources there. Tests look pretty much the same as in Perl:

# t/simple_tests.c

#include <stdio.h>
#include "tap.h"
#include "something.h"
int
main(void)
{
    plan_tests(1);

    /*
     * A simple example of a test.
     */
    ok(1 + 1 == 2, "Basic arithmetic works");
    return exit_status();     /* Return the correct exit code */
}
[download]

A simple t/Makefile.am could look like this:

# binaries
check_PROGRAMS = simple_tests

simple_tests_SOURCES = simple_tests.c tap.c  ../src/something.c\
                 tap.h ../src/something.h

simple_tests_CFLAGS = -Wall --pedantic -std=c99 -I ../src

TESTS = simple_tests
[download]

Then add 't' in your main Makefile.am:

SUBDIRS = src t
[download]

Then you can run the tests with 'make check'.

---

---

• 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.