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


Ignore:
Timestamp:
Jul 7, 2012, 6:56:09 PM (7 years ago)
Author:
Xiaochen Pan
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Projects/GSoC/TestingReview/Cmockery

    v3 v4  
    44Cmockery is a lightweight and highly portable unit testing framework with minimum conflicts with standard C library headers.
    55
    6 + 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.
     6 * 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.
    77
    8 - 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.
     8 * 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.
    99
    10 + 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.
     10 * 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.
    1111
    12 + Cmockery provides a more detailed tests report than CMock by providing the reason for tests failures.
     12 * Cmockery provides a more detailed tests report than CMock by providing the reason for tests failures.