anporumb
anporumb
at the moment, there's a (1x) global TEST_SUITE_INITIALIZE and a (1x) global TEST_FUNCTION_INITIALIZE. This does not leave much flexibility in setting up the initial conditions for a test. A test...
When ```c STRICT_EXPECTED_CALL(function(args...)) .CopyOutArgument_gaga(&source, sizeof(source)); ``` is used AND function has a hook registered the hook WILL get called. This should not happen, and CopyOutArgument should behave like .SetReturn() and...
umock_c says: "Failed parsing argument va value from the call." Here's repro: https://github.com/Azure/umock-c/tree/napo_parse_error_of_arguments This happens when running `umock_c_int_exe_umock_c` tests. Suspicion of parser failing when confronted with an unbalanced number of...
Right now the behavior or MOCKABLE_FUNCTION is that between `#define ENABLE_MOCKS` / `#undef ENABLE_MOCKS` will generate code. This improvement wants to have MOCKABLE_FUNCTION generate SEPARATE "proper declarations for a header"...
Right now I have: ```c STRICT_EXPECTED_CALL(create_something("a", 1)); ``` But I want to have: ``` STRICT_EXPECTED_CALL(create_something("a", 1), "%s %d", "create_something for source", __LINE__); ``` And these printf-ish arguments would be printed...
Those 2 headers would contain #define ENABLE_MOCKS respectively #undef ENABLE_MOCKS #include "umock_c/umock_c_prod.h" and should have a mechanism where 1. "umock_begin_mocks.h" after "umock_begin_mocks.h" is error 2. "umock_end_mocks.h" without "umock_begin_mocks.h" is error...
(this is for C++).  yields  Here's a simple repro: ```cpp typedef enum E {A,B,C} E; void f(E e) { (void)e; } int main(void) { f(0); f(A); return 0;...
Will always return the value from MOCKABLE_FUNCTION_WITH_RETURNS :( for the "positive" case.
At the moment umock_c mechanism of expected/actual call matching is enables globally. There's a mechanism to reset all the calls (umock_c_reset_all_calls()). But that is rather brutal. I propose to have...
1. ValidateArgumentBuffer does not have a "a name" (doesn't expand to ValidateArgumentBuffer_result where "result" is the name of the parameter) 2. Would be nice to have ValidateArgumentBuffer understand structures. ValidateArgumentBuffer_result_some_struct_field(&is_true,...