Google Code Exporter
Google Code Exporter
``` What steps will reproduce the problem? 1. Compile and execute assert_module_test.c on LP64 platform. 2. Observe crash in setjmp. What is the expected output? What do you see instead?...
``` What steps will reproduce the problem? 1. Compile on LP64 platform. 2. Observe gcc warning messages. What is the expected output? No warnings. What do you see instead? /Users/smb/src/cmockery-staging/osx/../src/cmockery.c:...
``` What steps will reproduce the problem? 1. Compile on LP64 platform such as Mac OS X or Linux on x86_64 2. Observe warning messages. What is the expected output?...
``` What steps will reproduce the problem? 1. Compile on LP64 platform such as Mac OS X or Linux on x86_64 2. Observed compiler warning messages. What is the expected...
``` What steps will reproduce the problem? 1. create the following unit test of cmockery: /*** * @unit_test assert_in_range with signed int. */ void test_assert_in_range_signed_int(void **state) { int value; int...
``` What steps will reproduce the problem? 1. Compile cmockery using gcc version 4.2.1. 2. Observe warning messages. What is the expected output? No warnings What do you see instead?...
``` What steps will reproduce the problem? 1. gcc/g++ warns when compiling cmockery.c with some options such as -Wall What is the expected output? What do you see instead? no...
``` What steps will reproduce the problem? When testing a function, say "foo", that uses "printf", if I a mock "printf" using mock() and check_expected() and write a test for...
``` Hi! I think adding the standard required headers within #if/#endif would reduce the code needed to bootstrap a new test. #ifndef CMOCKERY_NO_STANDARD_HEADERS #include #include #include #endif ``` Original issue...
``` What steps will reproduce the problem? 1. compile the standard cmockery example 'assert_macro_test.exe' on Windows 2. execute "assert_macro_test.exe 1>output 2>&1" What is the expected output? What do you see...