Home/ Questions/Q 97737
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T00:03:43+00:00

I’m working on an embedded C project that depends on some external HW. I

  • 0

I’m working on an embedded C project that depends on some external HW. I wish to stub out the code accessing these parts, so I can simulate the system without using any HW. Until now I have used some macros but this forces me to change a little on my production code, which I would like to avoid.

Example:

stub.h #ifdef _STUB_HW #define STUB_HW(name) Stub_##name #else /*_STUB_HW*/ #define STUB_HW(name) name #endif /*_STUB_HW*/  my_hw.c WORD STUB_HW(clear_RX_TX)() { /* clear my rx/tx buffer on target HW */ }  test_my_hw.c #ifdef _STUB_HW WORD clear_RX_TX() { /* simulate clear rx/tx buffer on target HW */ }

With this code I can turn on/off the stubbing with the preprocessor tag _STUB_HW

Is there a way to acomplish this without having to change my prod code, and avoiding a lot of ifdefs. And I won’t mix prod and test code in the same file if I can avoid it. I don’t care how the test code looks as long as I can keep as much as possible out of the production code.

Edit:

Would be nice if it was posible to select/rename functions without replacing the whole file. Like take all functions starting on nRF_## and giving then a new name and then inserting test_nRF_## to nRF_## if it is posible

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I just make two files ActualDriver.c and StubDriver.c containing exactly the same function names. By making two builds linking the production code against the different objects there is no naming conflicts. This way the production code contains no testing or conditional code.

    • 0