Changes between Version 3 and Version 4 of Projects/GSoC/TestingReview/CMock

Timestamp:

07/07/12 00:03:27 (12 years ago)

Author:

Xiaochen Pan

Comment:

Projects/GSoC/TestingReview/CMock

@@ -2 +2 @@
 
 
-Cmockery is a lightweight and highly portable unit testing framework with minimum conflicts with standard C library headers. 
+CMock is a highly automated testing framework based on Unity, a unit testing framework. It have also provided handy tools supporting mocking functionality. 
 
-+ It is well suited to work for RTEMS based testing thanks its effort to avoid relying on new features of compilers, and also its lightweight and minimum-conflict headers. It also works well for Host based tests too. 
++ With the heavy usage of Ruby, which enables the high level of automation, comes with highly strict test-writing format and light tests writing effort compared to other testing frameworks supporting mocking functionality. 
 
-- Unlike CMock, Cmockery has a relatively less stringent format requirements, while it requires the tester to write the test runner and mock functions by hand, while both of which can be automatically generated by scripts in Cmock. For mock function implementations, Cmock testers only need to define the expect input and output for certain functions in unit tests, where the mock functions are generated by ruby script according to the header files, which is convenient and easy to use. However, with Cmockery, testers need to write the mock functions by hand, which is troublesome for test automation and sometimes confusing. 
++ It is well suited for both RTEMS based and Host based testing, where RTEMS-based testing is hard to guarantee for a large number of  tests frameworks.
 
-+ Cmockery provides convenient interface to test for memory leaks, buffer underflow and buffer overflow, all of which would cause fatal errors for single processed RTEMS system. 
++ It supports several compilation options, such as CMOCK_MEM_STATIC and CMOCK_MEM_SIZE, the combination of which limits the total amount of memory the testing program could use during run time. If the tests needs more memory than specified, it quit tests. Also, there are a lot of other compilation options that facilitate testing under embedded environments. 
 
-+ Cmockery provides a more detailed tests report than CMock by providing the reason for tests failures.
++ The tests results are reported with line number and function names indicated. 
+
++ The scripts-rich feature have largely automated test running process. 
+
++ CMock also supports setUp() and tearDown() functions runned before and after each test functions, which is similar to concepts in test fixtures. 
+
++ Unlike other test framework evaluated, it is upgradable to Ceedling, which is a script driven framework based on CMock and Unity.