announce: New Google C++ Testing Framework

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Zhanyong

    announce: New Google C++ Testing Framework

    Hi,

    We are glad to announce that today we have open-sourced Google C++
    Testing Framework (http://code.google.com/p/googletest/), a library
    that helps you write better C++ tests.

    You can read more about the release at
    http://googletesting.blogspot.com/20...c-testing.html.
    Please send comments and questions to
    googletestframe work@googlegrou ps.com.

    Looking forward to hearing from you!
    --
    Zhanyong Wan
    Software Engineer
    Google
  • phlip

    #2
    Re: announce: New Google C++ Testing Framework

    Zhanyong wrote:
    When they fail during debugging, does the debugger stop at a breakpoint on the
    failing ASSERT_ or EXPECT_ line?

    Comment

    • vladlosev@gmail.com

      #3
      Re: announce: New Google C++ Testing Framework

      It has a command line option to do so.

      On Jul 3, 6:49 pm, phlip <phlip2...@gmai l.comwrote:
      Zhanyong wrote:>
      When they fail during debugging, does the debugger stop at a breakpoint on the
      failing ASSERT_ or EXPECT_ line?

      Comment

      • anon

        #4
        Re: announce: New Google C++ Testing Framework

        Zhanyong wrote:
        Hi,
        >
        We are glad to announce that today we have open-sourced Google C++
        Testing Framework (http://code.google.com/p/googletest/), a library
        that helps you write better C++ tests.
        >
        You can read more about the release at
        http://googletesting.blogspot.com/20...c-testing.html.
        Please send comments and questions to
        googletestframe work@googlegrou ps.com.
        >
        Looking forward to hearing from you!
        Almost the same as http://cxxtest.sourceforge.net/guide.html except your
        test framework is missing test macros for exceptions

        Comment

        • phlip

          #5
          Re: announce: New Google C++ Testing Framework

          anon wrote:
          Almost the same as http://cxxtest.sourceforge.net/guide.html except your
          test framework is missing test macros for exceptions
          How does it stack up to TestUnit++?

          (Zhanyong might notice we are listing the most well-reviewed C++ unit testers
          here...)

          Zhanyong Wan wrote:
          Phlip wrote:
          >Can the assertions do this?
          >
          No - I'd love to have that, but am not sure how you can do it in C++,
          which doesn't have reflection.
          >
          What we have is predicate assertions:
          >
          >
          GoogleTest - Google Testing and Mocking Framework. Contribute to google/googletest development by creating an account on GitHub.


          Your page does not explain that. That is Key-Yoot if it does this:

          ASSERT_PRED(ope rator<=, foo, bar);

          That also permits a lot of reflection. Your page _does_ say that when such as
          assertion fails, it prints out source text of foo and bar.

          Next, can your rig do the Abstract Test Pattern? That's hard unless you make
          registering test cases hard (like CppUnit does).

          --
          Phlip

          Comment

          • Zhanyong

            #6
            Re: announce: New Google C++ Testing Framework

            Hi, guys,

            Please send you comments to googletestframe work@googlegrou ps.com, as
            that's where we track discussions on Google Test.

            The Google Test FAQ (http://code.google.com/p/googletest/wiki/
            GoogleTestFAQ) now explains why we built Google Test instead of using
            an existing framework. You may find that useful.
            What we have is predicate assertions:
            >
            >http://code.google.com/p/googletest/...ncedGuide#Pred...
            >
            Your page does not explain that. That is Key-Yoot if it does this:
            >
            ASSERT_PRED(ope rator<=, foo, bar);
            >
            That also permits a lot of reflection. Your page _does_ say that when such as
            assertion fails, it prints out source text of foo and bar.
            I just checked again. The wiki says that the assertion prints the
            _values_ of foo and bar, and there are examples. :)
            Next, can your rig do the Abstract Test Pattern? That's hard unless you make
            registering test cases hard (like CppUnit does).
            It is being worked on - we have an experimental design but it's not
            final yet.

            If you have follow-up questions, please send to
            googletestframe work@googlegrou ps.com. Thanks!

            --
            Zhanyong

            Comment

            Working...