Boost unit testing main function?

Question

How do I define my own main() function when testing with boost?

Boost is using it's own main function, but I'm using a custom memory manager and it needs to be initialized before any memory is allocated, otherwise I'll get errors.

In C++, `main` is not a method. – jalf Sep 21 '12 at 11:32 — jalf, Sep 21 '12 at 11:32

Gennadiy Rozental · Accepted Answer · 2012-09-22T07:22:46.233

14

I do not believe you actually need your own main. I think you are much better off with global fixture:

struct AllocatorSetup {
    AllocatorSetup()   { /* setup your allocator here */ }
    ~AllocatorSetup()  { /* shutdown your allocator/check memory leaks here */ }
};

BOOST_GLOBAL_FIXTURE( AllocatorSetup );

edited Sep 22 '12 at 07:22

answered Sep 22 '12 at 07:13

Gennadiy Rozental

1,905
2
13
17

For the OP's purpose, this seems most appropriate. – Elliot Cameron Mar 25 '14 at 13:45

score 8 · Answer 2 · answered Sep 21 '12 at 18:13

8

You have to define

BOOST_TEST_NO_MAIN

before the boost includes.

BOOST_TEST_MAIN

is the default. http://www.boost.org/doc/libs/1_36_0/libs/test/doc/html/utf/compilation.html

answered Sep 21 '12 at 18:13

NomenNescio

2,899
8
44
82

score 0 · Answer 3 · answered Sep 21 '12 at 17:34

0

You can define a static object and his constructor will execute before main:

class Alloc_Setup {
   Alloc_Setup() {
       // Your init code
   }
   ~Alloc_Setup() {
       // Your cleanup
   }
};
Alloc_Setup setup;
int main() {} // (generated by boost)

answered Sep 21 '12 at 17:34

Galimov Albert

7,269
1
24
50

1

That's more of a hack than a solution, plus it doesn't allow you to define your own main function. No problem tough, I found the answer. – NomenNescio Sep 21 '12 at 18:14

Abyx · Answer 4 · 2012-09-21T11:36:38.040

-1

Memory can be allocated before main:

static int* x = new int(1);
int main() { return *x; }

And you could make your memory manager a global variable as well,
but you can't enforce a specific order of global variables initialization. (in standard C++ at least)

In Windows you could put your memory manager into a DLL, at it will be initialized before application entry point will be called, but still, something other may allocate a memory before - another DLL, or CRT of your DLL.

edited Sep 21 '12 at 11:36

answered Sep 21 '12 at 11:30

Abyx

12,345
5
44
76

1

The initialization order of globals is well defined inside a single compilation unit - so you _can_ enforce any order you want. Just place them in a single CU :) – Fiktik Sep 21 '12 at 17:50

Boost unit testing main function?

4 Answers4

Linked