Changes between Version 21 and Version 22 of Projects/GSoC/TestingReview/CMock

Timestamp:

07/08/12 20:14:21 (12 years ago)

Author:

Xiaochen Pan

Comment:

/* Host-based Test Result */

Projects/GSoC/TestingReview/CMock

@@ -62 +62 @@
 = Host-based Test Result =
 
+== Unity Output ==
+
 ''This is the test case''
 
@@ -76 +78 @@
 From the above, it can be seen that it reports single assert failures as well as test case running result. In the above screenshot, the line 2011 assert fails, and that test case passes with the macro VERIFY_FAILS_END at the end.
 The test summary shows that all 174 test cases have passed.
+
+In addition, with the ruby script, it can be seen that very large number of 174 test cases can be automated.
+== CMock Output ==
+
+''This compilation option in ruby script says that the total amount of memory can be used in tests is 32000 byte.''
+    prefix: '-D'
+    items:
+      - __monitor
+      - CMOCK_MEM_STATIC
+      - CMOCK_MEM_SIZE = 32000
+
+
+
+''The is the test case with mocking functions:''
+    void testMainShouldCallExecutorInitAndContinueToCallExecutorRunUntilHalted(void)
+    {
+          Executor_Init_Expect();
+          Executor_Run_ExpectAndReturn(TRUE);
+          Executor_Run_ExpectAndReturn(TRUE);
+          Executor_Run_ExpectAndReturn(TRUE);
+          Executor_Run_ExpectAndReturn(TRUE);
+          Executor_Run_ExpectAndReturn(FALSE);
+ 
+          AppMain();
+    }
+
+''In the above code, Executor_Init function is being mocked and expected to execute once in the AppMain() function. Executor_Run function is being mock with two different modes and is expected to run five times, with the top four times to return true and the fifth time to return false.''
+
+"This is the test result output:''
+
+  Creating mock for Executor...
+  gcc -D__monitor -DCMOCK_MEM_STATIC -D"CMOCK_MEM_SIZE = 32000" -DTEST -c -Isrc/ -I../src/ -I../vendor/unity/src/ -I../vendor/unity/examples/helper/ -Imocks/ -Itest/ ../vendor/unity/src/unity.c -obuild/unity.o
+  gcc -D__monitor -DCMOCK_MEM_STATIC -D"CMOCK_MEM_SIZE = 32000" -DTEST -c -Isrc/ -I../src/ -I../vendor/unity/src/ -I../vendor/unity/examples/helper/ -Imocks/ -Itest/ mocks/MockExecutor.c -obuild/MockExecutor.o
+  gcc -D__monitor -DCMOCK_MEM_STATIC -D"CMOCK_MEM_SIZE = 32000" -DTEST -c -Isrc/ -I../src/ -I../vendor/unity/src/ -I../vendor/unity/examples/helper/ -Imocks/ -Itest/ src/Main.c -obuild/Main.o
+  gcc -D__monitor -DCMOCK_MEM_STATIC -D"CMOCK_MEM_SIZE = 32000" -DTEST -c -Isrc/ -I../src/ -I../vendor/unity/src/ -I../vendor/unity/examples/helper/ -Imocks/ -Itest/ ../src/cmock.c -obuild/cmock.o
+  gcc -D__monitor -DCMOCK_MEM_STATIC -D"CMOCK_MEM_SIZE = 32000" -DTEST -c -Isrc/ -I../src/ -I../vendor/unity/src/ -I../vendor/unity/examples/helper/ -Imocks/ -Itest/ build/TestMain_Runner.c -obuild/TestMain_Runner.o
+  gcc -D__monitor -DCMOCK_MEM_STATIC -D"CMOCK_MEM_SIZE = 32000" -DTEST -c -Isrc/ -I../src/ -I../vendor/unity/src/ -I../vendor/unity/examples/helper/ -Imocks/ -Itest/ test/TestMain.c -obuild/TestMain.o
+  gcc -lm build/unity.o build/MockExecutor.o build/Main.o build/cmock.o build/TestMain_Runner.o build/TestMain.o -o build/TestMain.exe
+  build/TestMain.exe
+  test/TestMain.c:14:testMainShouldCallExecutorInitAndContinueToCallExecutorRunUntilHalted:PASS
+  -----------------------
+  1 Tests 0 Failures 0 Ignored
+  OK
+
+It can be seen from the above process that mocking functions are created automatically according to the specification of mocking behaviors stated in the above code. The test case testMainShouldCallExecutorInitAndContinueToCallExecutorRunUntilHalted has passed.