Quiet output

[GoogleCodeExporter]

There is no flag to pass to InitGoogleTest that results in minimal console 
output. Such a flag would tell gtest to only output errors from failed tests, 
the number of tests passed, and the total time elapsed. This flag is necessary 
if one wants to compile all tests into a executable to be run as a post-build 
step.

Original issue reported on code.google.com by [email protected] on 4 Mar 2011 at 8:41

[GoogleCodeExporter]

This can be done by the user by implementing a simple event listener that 
prints whatever information the user wants.  See the "advanced guide" wiki for 
how to do it.

Also, please send feature requests to the mailing list instead of the issue 
tracker.  Thanks!

Original comment by [email protected] on 9 Mar 2011 at 7:30

• Changed state: WontFix
• Added labels: OpSys-All, Priority-Low, Type-Enhancement, Usability
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Thank you!

Original comment by [email protected] on 28 Apr 2011 at 4:09

[joshkel]

A couple of semi-standard solutions that have come out since this issue was first raised:

• This gist contains a sample ConfigurableEventListener decorator that allows selectively enabling or disabling output types.
• My Google Test Pretty Printer significantly shortens GTest's output.

[metal4people-zz]

Still believe this feature should be available out of the box, because there are a lot of tests already written and to achieve the behavior you would need to add listener to all of them.
Instead having commandline option --quite or something like that would save a lot of time.

[gennadiycivil]

Thank you very much for this report. The best way to approach this would be to create a proper PR and submit it for consideration.

[metal4people-zz]

No problem. You know I've found better way to reach my aim.
I think most of people needs the same is to use: --gtest_repeat and --gtest_break_on_failure.
For example: --gtest_repeat=100 --gtest_break_on_failure will run tests 100 times, but once something fails it stop tests execution.
Very convenient.
Thank you guys!

[gennadiycivil]

Great to hear. I suggest submitting a patch to the documentation so others can benefit. Thanks G

…

On Sat, Jan 26, 2019, 08:21 metal4people ***@***.*** wrote: No problem. You know I've found better way to reach my aim. I think most of people needs the same is to use: --gtest_repeat and --gtest_break_on_failure. For example: --gtest_repeat=100 --gtest_break_on_failure will run tests 100 times, but once something fails it stop tests execution. Very convenient. Thank you guys! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#358 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMJSMhiK0aqRzo23sKzbO3RKmjE5yU-Uks5vHFY8gaJpZM4MVAWH> .

[moof2k]

+1 for this being an out-of-the-box feature