Databases
StackOverflow2013
Postsdbo
POGoogleTest vs CppUnit: The facts
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGoogleTest vs CppUnit: The facts
    primarykey
    data
    text
    <p>In the process of setting our C++ unit testing framework for the next years we shortlisted <strong>GoogleTest</strong> and <strong>CppUnit</strong>. I have some experience with both and my heavy preference is GoogleTest. Anyways to convince my boss I need some <strong>facts</strong> so I did some reading on the Internet, including the manuals, wiki pages and some of the sources. I came up with a list of GoogleTest advantages and a single CppUnit advantage(graphic test runners). Here they are ordered by <strong>perceived</strong> usefulness: </p> <ul> <li>INSTANTIATE_TEST_CASE_P to instantiate a test case with any set of parameters you want, including Cartesian products </li> <li>FRIEND_TEST for testing private class members(for all the legacy code) </li> <li>turning asserts into breakpoints </li> <li>non-fatal asserts </li> <li>"out of the box" googlemock integration </li> <li>automatic tests detection, no need to enumerate them</li> <li>tests can be disabled and enabled </li> <li>tests to run can be selected using name patterns </li> <li>value/type-parameterized tests </li> <li>user-defined predicate asserts </li> <li>death tests </li> <li>much richer set of asserts </li> <li>type asserts </li> <li>asserting on subroutines </li> <li>additional debug info can be added to asserts using &lt;&lt; </li> <li>RecordProperty emits last value of property to the XML output </li> <li>SCOPED_TRACE helps understand the context of an assertion failure coming from inside a sub-routine or loop. </li> <li>xUnit XML output, can be shown by Jenkins right away without a XSLT transformation in between </li> <li>supports custom types printers</li> <li>time consumed by test indication(I suspect this is also possible with CppUnit but I haven figured it out yet) </li> <li>test event listener API (user-defined plug-ins) </li> <li>test shuffling </li> <li>no exceptions and RTTI </li> </ul> <p>Am I correct in assuming that all of the above are not supported by CppUnit? Is there an useful GoogleTest feature <strong>not available</strong> in CppUnit I am missing? </p> <p>And last but not least: Are there any nice CppUnit features that GoogleTest <strong>lacks</strong>? </p> <p>Thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USEstuansInterius
    1. USEstuansInterius
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGoogleTest vs CppUnit: The facts
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGoogleTest vs CppUnit: The facts
      1. USAntonio Pérez
      1. VTFavorite
    3. VO
      singulars
      1. POGoogleTest vs CppUnit: The facts
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSome of the answers to [Comparison of c++ unit test frameworks](http://stackoverflow.com/questions/242926/comparison-of-c-unit-test-frameworks) specifically address GoogleTest features.
      singulars
      1. POGoogleTest vs CppUnit: The facts
      1. USGreg Hewgill
    2. COA couple of years ago I was doing a similar survey, GoogleTest was not around then. I settled on CXXTest which had a mechanism to enumerate the test cases by a pre-parsing step with Perl. That was vastly superior to CppTest. That said, I know nothing about GoogleTest.
      singulars
      1. POGoogleTest vs CppUnit: The facts
      1. USWolfram Arnold
    3. COA graphic test runner is an advantage? Usually you want something that can be automated easily, because automation means you get test feedback more easily and more often.
      singulars
      1. POGoogleTest vs CppUnit: The facts
      1. USBen Voigt
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload