You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(This is a feature request, I hope this is the right place for it.)
It would be nice to have some way to ignore calling order of mocked functions. E.g.
for (uint8_t i = 0; i < n; i++)
{
Cmock_start_ignore_call_order();
functionA_Expect(...);
functionB_Expect(...);
functionC_Expect(...);
functionD_Expect(...);
Cmock_stop_ignore_call_order();
}
In my case it does not matter, whether I call functionA first or functionD, what matters is that all of them are called with the correct values. Currently this can only be implemented with a lot of boilerplate, if I also want to check the parameter values (add stubs, set flags, use global vars, etc.).
The text was updated successfully, but these errors were encountered:
Thank you for your fast reply. If I understand you correctly, that setting is going to turn off order checking in all the tests in the project. What if I only want to apply it for a specific subpart of the tests (e.g. only 1 or 2 functions of the unit under test)? Is there a feature to solve that?
(This is a feature request, I hope this is the right place for it.)
It would be nice to have some way to ignore calling order of mocked functions. E.g.
In my case it does not matter, whether I call functionA first or functionD, what matters is that all of them are called with the correct values. Currently this can only be implemented with a lot of boilerplate, if I also want to check the parameter values (add stubs, set flags, use global vars, etc.).
The text was updated successfully, but these errors were encountered: