umock-c
umock-c copied to clipboard
Azure
A pure C mocking library
What is the definition of **install_library_includes** ??? [install_library_includes](https://github.com/Azure/umock-c/blob/master/CMakeLists.txt#L188) ```console CMake Error at CMakeLists.txt:188 (install_library_includes): Unknown CMake command "install_library_includes". Configuring incomplete, errors occurred! ``` I failed to build **umock-c** Cheers
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...
This will help identifying the offending STRICT_EXPECTED_CALL when defining negative tests. Example: ```c ... umock_c_negative_tests_snapshot(); size_t call_count = umock_c_negative_tests_call_count(); //act for (size_t i = 0; i < call_count; i++) {...
Current code might do something like this: ```c static void setup(int* optional_value) { if (optional_value != NULL) { STRICT_EXPECTED_CALL(foo(IGNORED_ARG)) .CopyOutArgumentBuffer_result(optional_value, sizeof(optional_value)); } else { STRICT_EXPECTED_CALL(foo(IGNORED_ARG)); } } ``` Would be...
Hello, I have trouble compiling some code using umock-c. The error I get is: ``` ../provisioning_client/samples/custom_hsm_example/../../deps/utpm/inc/azure_utpm_c/Marshal_fp.h:16:91: error: ISO C does not allow extra ‘;’ outside of a function [-Werror=pedantic] 16...
Hi, I working latest device updates sdk code and developed some own unit test for own customized part of code. Unit test is acting for function which send message to...
```Cmake include("${CMAKE_CURRENT_LIST_DIR}/umock_cTargets.cmake") include("${CMAKE_CURRENT_LIST_DIR}/umock_cFunctions.cmake") ```
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...