Improve stack traces on TestPartResult for EnhancedReporter

XMLWordPrintableJSON

    • Server Programmability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Stack trace:
        0xc56914b6963c: (anonymous namespace)::BSONObj_nullByteInStringBasic_Test::TestBody()
        0xc5691615d640: testing::internal::HandleSehExceptionsInMethodIfSupported<>()
        0xc569161426d4: testing::internal::HandleExceptionsInMethodIfSupported<>()
        0xc56916123fac: testing::Test::Run()
        0xc56916124a94: testing::TestInfo::Run()
      ... Google Test internal frames ... 

      GoogleTest appends an internal stacktrace in its TestPartResult. We should probably get rid of this. I don't think we should sift through the string output to remove the stack trace string we already have in TestPartResult. We can look into the google test flags to see if we can turn this off. We can also see if we have a need for stack traces in test results. If they are useful, we can add our own.

            Assignee:
            Alex Li
            Reporter:
            Alex Li
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: