a question for help about cmockery2

[lpabon]

This is the right place for a question. I'm checking your code now...

[lpabon]

Mocking is done by replacing during linking the actual function with your own. So you need to move funcb in func.c to another file, like funcb.c. Then build your unit test without including funcb.c, that way the linker will pick funcb() from test.c.

Here is an example:

$ ls
func.c funcb.c test.c
$ gcc -o func_unittest func.c test.c -lcmockery
$ ./func_unittest

Let me know if that helps

[jinwuxia]

I have tried this way as you said. It does work well. Thank you.

I also sovle this problem by adding macro to real funcb. Let the complier does not compile the real funcb but the mocked funcb.

//func.c
# ifndef UNIT_TESTING 
void funcb(int para)
{
para = para+10;
printf("real funcb\n");
}
#endif

void funca() 
{
int msg = 10;
funcb(msg);
}

in test.c,   #define UNIT_TESTING 1

But , from our users's view, the method you said or my macro solution above, has slightly changged the structure of the tested program files.

I think that whether cmockery can provide a internal mechanism to avoid modiying the structure of the tested program files, neither needing splitting the function nor adding macro explicitly.

I don't know wheter my thought is reasonable or not. Just only express my idea without other purpose.
Thank you again for your reply.

[lpabon]

@j123kaishichufa No problem at all. Your request is a good one, but C language make it really difficult to do this.

Instead what I have done in my projects is only mock external libraries. If I have a func.c and in that file I have funca() and funcb(), I would not mock them. Instead, if funca() calls funcx() which is in another directory or library, then I would create a mock_funcx().

Again, the goal is to make it simple and able to be maintained by others. Let me know if you need any other help.

[jinwuxia]

@lpabon
I think i have gotten your idea. Cmockery2 is really an lightweight test framework for unit test. It easy to use.
Thank you.