announce: New Google C++ Testing Framework

Zhanyong wrote:

Quote: http://googletesting.blogspot.com/2...-c-testing.html.

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

It has a command line option to do so.

On Jul 3, 6:49*pm, phlip <phlip2...@gmail.comwrote:

Quote: Zhanyong wrote: Quote: http://googletesting.blogspot.com/2...ew-google-c-tes..... > When they fail during debugging, does the debugger stop at a breakpoint on the failing ASSERT_ or EXPECT_ line?

Zhanyong wrote:

Quote: 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/2...-c-testing.html. Please send comments and questions to Join Bytes!. > 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

anon wrote:

Quote: 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:

Quote: Phlip wrote:

Quote: Quote: >Can the assertions do this?

Quote: Quote: >http://assert2.rubyforge.org/ > 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: > >

http://code.google.com/p/googletest...cate_Assertions

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

ASSERT_PRED(operator<=, 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

Hi, guys,

Please send you comments to Join Bytes!, 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.

Quote: Quote: What we have is predicate assertions: > >http://code.google.com/p/googletest...ancedGuide#Pred... > Your page does not explain that. That is Key-Yoot if it does this: > ASSERT_PRED(operator<=, 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. :)

Quote: 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
Join Bytes!. Thanks!

--
Zhanyong