Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

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


Ignore:
Timestamp:
07/07/12 02:54:39 (12 years ago)
Author:
Xiaochen Pan
Comment:

Legend:

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

    v3 v4  
    22
    33
    4 Google Test is unit testing framework conforming to xUnit architecture. Google Mock is a library that can be used to provide mocking functionality to other C++ testing frameworks as well. They can be used in combination for host based testing.
     4Google Test is unit testing framework conforming to xUnit architecture. Google Mock is a library that can be used to provide mocking functionality to Google Test and other C++ testing frameworks as well. They can be used in combination for host based testing.
    55
    66+ By defining a strict test format, Google Test supports automatic test discovery.
     
    1010+ Google Test  provides a rich set of assertions, and even user-defined assertions for more readable tests results display. It has provided three flexible ways for user to define custom assertions, using existing boolean functions, use AssertionResult object, and using Predicate-formatter to further customize error messages.
    1111
    12 + Google Test provides a mechanism to verify that unit tests fails or exit with give exit code or error message.
     12+ Google Test provides a mechanism to verify that unit tests fails or exit with right exit code or error message.
    1313
    1414+ Google Test supports parameterized tests, which can be very convenient in tests automation.
    1515
    16 + Test error propagation options have made it possible to write complicated unit tests with subroutines. In detail, this option has made it possible to avoid memory corruption due subroutine error and thus to avoid causing the other tests which have called the subroutine to go unexpected.
     16+ Test error propagation options have made it possible to write complicated unit tests with subroutines. In detail, this option has made it possible to avoid memory corruption due to subroutine error and thus to avoid causing the other tests which have called the subroutine to go unexpected.
    1717
    1818+ It also supports various options for running the tests,for example, tests repetition, independent tests running, tests shuffling.