Forum Discussion

Yariv_Amar's avatar
Yariv_Amar
Contributor
13 years ago

[Resolved] lack of details in Message Content Assertion

Hi

I'm using the great new feature "Message Content Assertion" - thanks for developing it. its makes assertions very easy !

the problem i have is that the error message in the logs and junit report is very shallow. for example:
----------------- Messages ------------------------------
[Message Content Assertion] Message Content Assertion failed : failed/compared = 1/16

When getting such an error during automation builds it's very hard to understand what's the failure.
I've tried to increase SoapUI log level, but w/o any success to get better message.

is it possible to get better message for this kind of error in the logs (like the one we get in the GUI)?
For example i'd expect to see in the logs / Junit report:
----------------- Messages ------------------------------
[Message Content Assertion] Message Content Assertion failed : failed/compared = 1/16
SHUTDOWN_APPROVAL_TIME [2012-1-10.12.7. 20. 0] did not meet condition related to [2012-01-10 10:07:00]

Thank you.
  • Hi!

    No sorry, there is currently now way to get the specific error messages from the Error message column in the Message content assertion dialog in the reports.
    Would you like to submit a feature request for this?

    --
    Regards

    Erik
    SmartBear Sweden
  • Yes -i want to open a request for fixing it.

    From my point of view it's a bug - not a feature.
    On every other assertion the message is "expected XXX actual is YYY" - why this case is different?
  • Hi again!

    I've now registered a feature request for this in our internal issue tracker: SOAPUI-4582

    --
    Regards

    Erik
    SmartBear Sweden