Changes between Version 7 and Version 8 of Projects/GSoC/TestingReview/Cmockery


Ignore:
Timestamp:
Jul 8, 2012, 8:50:33 AM (7 years ago)
Author:
Xiaochen Pan
Comment:

/* General Comparison */

Legend:

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

    v7 v8  
    77 * 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.
    88
    9  * 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.
     9 * 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. To write mock functions, 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 more convenient and easier than Cmockery.
    1010
    1111 * 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.
    1212
    13  * Cmockery provides a more detailed tests report than CMock by providing the reason for tests failures.= RTEMS based Test Results =
     13 * Cmockery provides a more detailed tests report than CMock by providing the reason for tests failures.
     14
     15 * Conforming to xUnit architecture makes Cmockery more competitive than CMock in respect of test case relationships.
     16= RTEMS based Test Results =
    1417= sp01 test =
    1518