Table Of Contents

Previous topic

fctcl: Command Line API

Next topic

fctstr: String API

This Page

FCTMF: Multi-file API

New in version 1.1: The FCTX Multi-File (FCTMF) supersedes the older “include method” described in version 1.0.


When you start unit testing with FCTX you will find that at some point holding all your tests in one file can become unwieldy. The Multi-File api (FCTMF) attempts to provide a minimal barrier to writing unit tests that span multiple files.

The idea is to have one file that starts up tests defined in each of the other files. The process of registration is a one step “call” into the other files.

Multi-File Setup

Imagine we have two files: test_main.c and test_a.c. In test_main.c we will setup and register our test that is defined in test_a.c.

Lets look at test_main.c,

/* file: test_main.c */

#include "fct.h"

} FCT_END();

there now we have set it up to call into the test suite called “test_a_feature” defined in test_a.c. Lets look at the contents of test_a.c.

/* file: test_a.c */

#include "fct.h"

FCTMF_SUITE_BGN(test_a_feature) {

    FCT_TEST_BGN(sanity_check) {
        fct_chk( a_feature__sanity_check() );
    } FCT_TEST_END();


this will register a test suite called “test_a_feature” and execute a test called “sanity_check”.

If you wanted to use a test suite with fixtures (setup/teardown), you would do the following,

/* file: test_a.c */

#include "fct.h"

static a_object_t *obj;

FCTMF_FIXTURE_SUITE_BGN(test_a_feature) {

        obj = a_object_new();
    } FCT_SETUP_END();

        obj =NULL;

    FCT_TEST_BGN(sanity_check) {
        fct_chk( a_object__sanity_check(obj) );
    } FCT_TEST_END()


the only difference here being the introduction of “FIXTURE” into scope statements as well as the SETUP and TEARDOWN fixtures themselves.

The key thing to also notice is that all the testing, checking, setup and teardown macros follow the existing FCT module.

Note for MVC Compilers

Using the FCTMF API with warning level 4 will produce the following:

warning C4210: nonstandard extension used : function given file scope

so far testing both with MVC and GCC FCTMF has yet to fail, except for this warning level above.

So what’s happening here?

The FCTMF_SUITE_CALL uses the following little trick whereby,



void my_test_suite(fctkern_t *fk);

where we make a “variable” and “run it”, and let the linker sort it out all in the end.

The goal here was to prevent you from having to repeatedly “register” your test suite in order for you get up and running. To stay at warning level 4, but quite the compiler, you can do the following,

#if defined(_MSC_VER)
#   pragma warning(push, 3)
#endif /* _MSC_VER */
#if defined(_MSC_VER)
#   pragma warning(pop)
#endif /* _MSC_VER */

and you will be able to continue to use /W4 with MVC as well as GCC.

Multi-File Test Suites


This launches the test suite defined by name. You would place this call between the FCT_BGN() and FCT_END() scope. This simply calls off to another file, and it does not prevent you from having other tests within the FCT_BGN() and FCT_END() scope.

For Visual Studio 6 compilers, you will need to use the FCTMF_SUITE_DEF() function.


Following the xtest convention, every test suite needs to start with a SUITE_BGN function. In by using the FIXTURE variants you are indicating that you wish to install a SETUP and TEARDOWN fixture via the FCT_SETUP_BGN() and FCT_SETUP_END() and FCT_TEARDOWN_BGN() and FCT_TEARDOWN_END() functions.



This closes a test suite that contains fixtures. If you do not wish to specify a setup/teardown you would use the FCT_SUITE_END() function instead.


Use this FCTMF_SUITE variant if you do not want to bother specifying a SETUP and TEARDOWN blocks.



Closes the FCTMF_SUITE_BGN() function.


Defines a test suite with the given name. This is only required for the Visual Studio 6 compilers (or if you choose to avoid the comments in Note for MVC Compilers). This call must be made before the FCT_BGN() function. The name must be the same as the name in FCTMF_SUITE_CALL() and FCTMF_SUITE_BGN().