Recent changes to 9: No logging of the exception throw

#9 No logging of the exception throw

Philip Wardlaw — Thu, 01 May 2014 20:22:26 -0000

I can suggest the following fix, Although it may not work for more sophisticated outputs (html etc.)

Modify lines 180 of src/suite.cpp onwards as follows:

catch (std::exception& e) {
    std::cout <<  "\tError:   An exception was thrown during test '" << data._name <<"()'" <<  std::endl;
    std::cout << "\tDetails: " << e.what() <<  std::endl;
    _suite._result = _suite._success = false;
}

Text output:

SolutionVariableTest: 3/4
Error: An exception was thrown during test 'testSolMap()'
Details: You have already added a SolutionVariable of corresponding VariableNames type to SolutionMap
SolutionVariableTest: 4/4
SolutionVariableTest: 4/4, 75% correct in 0.000466 seconds

#9 No logging of the exception throw

Sebastian Pipping — Thu, 01 May 2014 18:48:33 -0000

I might find time to review patches, but that's all, I'm afraid.

#9 No logging of the exception throw

Philip Wardlaw — Thu, 01 May 2014 18:46:06 -0000

Has anything been done on this bug? I don't mind if there is no rigorous exception handling, but printing out e.what() would be very beneficial. It is very confusing for developers when a test fails due to an exception, and there is no output explaining this from CppTest.

No logging of the exception throw

Dzmitry Liauchuk — Sat, 22 May 2010 09:44:28 -0000

When an exception is thrown within TEST_ASSERT then the whole function is reported as 0% successful. However, there is no information about what is the reason of 0% result and at what line the exception is thrown which makes fixing the problem harder.
I propose to change TEST_ASSERT to add information to the report that unexpected exception is thrown and log also the line and file where the TEST_ASSERT is invoked.