Got it what you mean by.
Though that assertion has Error Message as last column in that table while defining the Message Content Assertion, that is not being show to the user in the reports. Is that expected or not, I have no clue, it can be confirmed by Smartbear team.
But if the same error message is shown probably it would have been useful to the user, in my opinion. May be the same can be bring to Smartbear attention to get that addressed.
If we take yours as an example, you have 4 checks in one assertion. It might be showing something as below if 2 of them failed.
Message Content Assertion failed : failed/compared = 2/4
Irrespective of that, you may have to rerun the test once the fixes are available, and make sure entire assertion is passed instead of partial pass.
The alternative at the moment would be, if at all the details are needed until the Smartbear revert back saying or confirming the issue and updates available, to use separate xpath assertions. Of course, it defeats the MCA assertion type.
By the way, I could try another alternative with the MCA(instead of xpath) with single property check(since multiple not working) and following are results(renamed MCA to below value) and at least the message is clear:
[Is conversion rate equal to 65?] Message Content Assertion failed : failed/compared = 1/1 [Is conversion rate equal to 70?] Message Content Assertion failed : failed/compared = 1/1
Thank you for your time for taking time to explain the problem.
From the first message in this thread, I see this information,
"In my tests, I use a lot of "message content assertions". But when one of those fail, I can't seems to find the reason of the failure in the report."
So, you mean you have used multiple MCA assertions and you could not able to point out which assertion has failed in the overall JUnit styled XML report generated. Correct?
Also, I tried reproducing the behavior and could see expected outcome while running through Ready! API 1.4.1. Please find below the details,
Jenkins would call below command,
testrunner.bat -s"Directions API TestSuite" -c"Simple Tests" -a -j -fC:\Users\jayarak1\Desktop\Demo -R"TestCase Report" -E"Default environment" "C:\Don't Delete\Sample Project\Google Maps REST\Google-Maps-soapui-project - REST XML.xml"
I got the report generated in XML format and see a detailed error note for MCA assertions,
----------------- Messages ------------------------------ [Match content of [bounds]] XPathContains assertion failed for path [declare namespace ns1='http://maps.googleapis.com/maps/api/directions/json'; //ns1:Response[1]/ns1:routes[1]/ns1:e[1]/ns1:bounds[1]] : Exception:org.custommonkey.xmlunit.Diff [different] Expected text value '45.5101458' but was '45.5017123' - comparing <lat ...>45.5101458</lat> at /bounds[1]/northeast[1]/lat[1]/text()[1] to <lat ...>45.5017123</lat> at /bounds[1]/northeast[1]/lat[1]/text()[1] [Check number of steps [12]] XPathContains comparison failed for path [declare namespace ns1='http://maps.googleapis.com/maps/api/directions/json'; count( //ns1:Response/ns1:routes/ns1:e/ns1:legs/ns1:e/ns1:steps/ns1:e)], expecting [13], actual was [16]
Since, I have used -a switch, SoapUI helps me in exporting test case wise results. Please try rerunning the command with above specified options and let us know the results.
Thanks,
Samy
kondasamy wrote:So, you mean you have used multiple MCA assertions and you could not able to point out which assertion has failed in the overall JUnit styled XML report generated. Correct?
Incorrect. I'm able to pinpoint which MCA failed, what I'm unable to do is to know, in the failing MCA, which values were wrong.
ok! Have you tried the option which I meant about using -a switch?
AlumniHi Marcl,
As far as I see, you’ve contacted the Ready! API Support team regarding this question, and they have created a product improvement idea to improve the message in the test log. I hope this will be implemented soon.
