Mocking Opaque Types

RE: Mocking Opaque Types

Menon — Thu, 18 Jul 2024 08:38:44 GMT

Hello Jesse,

Thanks for providing the update; it's good to hear that you've made some progress. Let me know if I need to escalate this issue to get an expert opinion, as I am not an expert on this topic. Please note that there might be some delay in getting an update due to the summer vacation period in Norway.

Kind regards,

Abhijith

RE: Mocking Opaque Types

Jesse_Carpenter — Tue, 16 Jul 2024 13:11:11 GMT

I've come to a temporary solution by defining the struct bt_conn within my source file, with compiler tags around it so that this definition is only used when I'm testing. I have yet to actually test this, but it at least compiles for now.

#ifdef TESTING
typedef struct bt_conn {
    int dummy;
} bt_conn;
#endif

RE: Mocking Opaque Types

Jesse_Carpenter — Mon, 15 Jul 2024 15:05:52 GMT

I also came across this post, but I cannot add a fake definition of bt_conn in the autogenerated cmock header that will exist across builds.

RE: Mocking Opaque Types

Jesse_Carpenter — Mon, 15 Jul 2024 13:58:43 GMT

Hi Abhijith,

So the actual function call already calls a pointer. Thats on me for not being specific enough. Here's the function:

void on_sent(struct bt_conn *conn, void *user_data);

I have many more functions that I'll need to test later that also call bt_conn as a pointer.

I tried defining the argument as not a pointer as well, but still get the same issue. When I try defining the type struct bt_conn within my test file, and even give it some meaningless content, the error still persists. When I brought this up on the discord, they suggested making my own mocks of all of the functions and even mocking the struct itself by hand, however I don't believe this will allow me to continue using Unity they way that I already have been. If you could please escalate this ASAP I would greatly appreciate it.
-Jesse

RE: Mocking Opaque Types

Menon — Mon, 15 Jul 2024 09:38:41 GMT

Hello,

Sorry for the delay in responding. I'm also not very familiar with opaque types and Cmock. The log you uploaded indicates there was a build issue because the code attempted to determine the size of a type, const struct bt_conn, which was not fully defined at that point. This problem occurred in the mock function __cmock_on_sent generated by CMock. To potentially resolve issues related to incomplete type definitions, could you try using a pointer to struct bt_conn (struct bt_conn *conn) instead of (struct bt_conn conn)?

Please let me know if this solution works for you. Otherwise, I will escalate the issue internally to someone with more experience.

Kind regards,

Abhijith