INFO messages to output?

[Michael Ellery]

I'm looking for way to add an informational message to the output from the test framework - to annotate the output, essentially.  Some frameworks have implemented this kind of functionality as a NOTE() or INFO() macro. Does gtest have anything that fits this purpose?  Advice appreciated.

-Mike Ellery

[Keith Ray]

ASSERT_*(...) << "Additional text".

Most of assertions can print extra text when they fail. Check the header files.

C. Keith Ray

http://agilesolutionspace.blogspot.com/

twitter: @ckeithray

On Apr 28, 2014, at 2:26 PM, Michael Ellery <melle...@gmail.com> wrote:

I'm looking for way to add an informational message to the output from the test framework - to annotate the output, essentially.  Some frameworks have implemented this kind of functionality as a NOTE() or INFO() macro. Does gtest have anything that fits this purpose?  Advice appreciated.

-Mike Ellery

--

---
You received this message because you are subscribed to the Google Groups "Google C++ Testing Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googletestframe...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Ellery]

Yes, the message support in assertions is quite handy, but I'm looking for a way to *always* print some diagnostic output, regardless of assertion failure.

Thanks,
Mike

[John D]

Does ASSERT(false) count?

[BarbaraJoy Jones]

That would introduce an artificial failure in every test that used it, which makes it a lot harder to read the test output or use automatic test tools.

I use a custom event listener: https://code.google.com/p/googletest/wiki/AdvancedGuide#Extending_Google_Test_by_Handling_Test_Events

It's mostly for the test output to a file (using the same format as stdout).

It also prints any messages streamed to the SUCCEED macro to both that file and stdout.

https://code.google.com/p/googletest/wiki/AdvancedGuide#Explicit_Success_and_Failure

[Samuel Benzaquen]

On Mon, Apr 28, 2014 at 4:09 PM, Michael Ellery <melle...@gmail.com> wrote:

Yes, the message support in assertions is quite handy, but I'm looking for a way to *always* print some diagnostic output, regardless of assertion failure.

Is SCOPED_TRACE() what you are looking for?

https://code.google.com/p/googletest/wiki/AdvancedGuide#Adding_Traces_to_Assertions

_Sam

 

Thanks,
Mike

On Monday, April 28, 2014 1:00:27 PM UTC-7, keith.ray wrote:

ASSERT_*(...) << "Additional text".

Most of assertions can print extra text when they fail. Check the header files.

C. Keith Ray

http://agilesolutionspace.blogspot.com/

twitter: @ckeithray

--

---
You received this message because you are subscribed to the Google Groups "Google C++ Testing Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googletestframe...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

[Michael Ellery]

Barbara,

Thanks for that advice - it looks like a custom listener might do the trick for me, although I will need to disable/enable the "always print" aspect of the listener depending on the context of the test (which seems doable)

-Mike

[BarbaraJoy Jones]

I have a command-line option to control whether the listener writes to the file, but it always prints the SUCCEED messages because that's rather important for the way we use that macro in our test code.

It sounds like it would be simpler if you put the enable/disable logic within your tests.

The relevant code from my listener is extremely simple:

void FilePrinter::OnTestPartResult(const TestPartResult& result)

{

    std::string part = FormatTestPartResult(result);

    // calls to SUCCEED() should also go to stdout

    if(result.type() == TestPartResult::kSuccess)

        printf("%s\n", part.c_str());

    logger.writeToFile(part);

}

The FormatTestPartResult method just returns a string containing the same information as the default test output with some extra line breaks and a timestamp. I think that I copied most of it from the gtest code for printing test results.