Contributions
Re: bug in "Message Content Assetrion" with dates
Hi Thank you Renato. We are now using Groovy script to overcome this glitch, the groovy is familiar with both formats, and does the assertion correctly. Although it works, I don't like it . -- I'm not sure I can change the Oracle system as this DB contains many schemas\users for other projects too (I will ask our DBA). I was looking for the same configuration on the client side. Thanks to your reply, we've rechecked our environments and discovered that we had several different ojdbc.jar versions in use. We will make sure that all users will have the same ojdbc.jar and that will resolve our issue. I guess that oracle driver have different date format / strategy on different driver version.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes0CommentsRe: bug in "Message Content Assetrion" with dates
Well, it's really a long time bug. I've used similar 'tricks' to get the logs and do validations using custom code. For dates we are still having lots of difficulties with their formatting. We are a team of developers and QE's working with a single SoapUI project that "talks" to our (single) integration web-server. In some tests we are querying and Oracle DB (using JDBC request) and we always have troubles with date-formatting. For some developers the date format on the JDBC response is: yyyy-MM-DD.HH.mm.s.SSSSSSSSS While for other developers the date format is: yyyy-MM-DD HH:mm. SSSSSSSSS As you can understand, it's very difficult to write assertions that works for everyone. (BTW, we worked-around it with groovy script). I thought it's related to the local of the end user, but all our locales are the same.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes0Comments- 12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes0Comments
Re: [Resolved] lack of details in Message Content Assertion
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?12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes0Comments- 12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes0Comments
bug in "Message Content Assetrion" with dates
I have a step that runs JDBC request to query an Oracle table and then validates the result using Message Content Assertion and Xpath. When I run the step on my machine (win) it works fine, but when it runs from Maven on our Hudson env. I get failure (see logs below). The problematic field type is (any) date-time, in my example DETECTION_TIME. the result from the DB is: <DETECTION_TIME>2012-12-25 11:00:00</DETECTION_TIME> in Message Content Assertion i wrote the value: 2012-12-25 11:00:00 This fails on our Maven run w/o details on the error (see the log below). In addition i've added another Xpath Assertion for the same field: Xpath: //Results[1]/ResultSet[1]/Row[1]/DETECTION_TIME[1]/text() Value: 2012-12-25 11:00:00 This assertion pass OK. There are 2 bugs here (to my opinion ) 1. Message Content Assertion for JDBC response does not validate dates properly when run from Maven 2. Message Content Assertion failure message is poor. it should say what was expected and what is the actual value in the logs. thanks, here is the relevant part from the log. 2013-01-06 17:19:54,891 INFO [SoapUIProTestCaseRunner] running step [Validate TimeDetection] 2013-01-06 17:19:54,960 INFO [log] this is the result as seen by groovy script: <ResultSet fetchSize="10"> <Row rowNumber="1"> <ID>b7c8c25c-e385-4bf4-b19b-e874155e2454</ID> <DETECTION_TIME>2012-12-25 11:00:00</DETECTION_TIME> <STATUS_TYPE_ENUM>ON</STATUS_TYPE_ENUM> </Row> </ResultSet> 2013-01-06 17:19:54,969 INFO [SoapUIProTestCaseRunner] Assertion [JDBC Status] has status VALID 2013-01-06 17:19:54,970 INFO [SoapUIProTestCaseRunner] Assertion [Match content of [DETECTION_TIME]] has status VALID 2013-01-06 17:19:54,971 INFO [SoapUIProTestCaseRunner] Assertion [Message Content Assertion] has status FAILED 2013-01-06 17:19:54,972 ERROR [SoapUIProTestCaseRunner] ASSERTION FAILED -> Message Content Assertion failed : failed/compared = 1/2 2013-01-06 17:19:54,974 ERROR [SoapUIProTestCaseRunner] Validate Edit Detection failed, exporting to [/o.../xxx_path removed_xxx/tion-0-FAILED.txt]12 years agoPlace ReadyAPI QuestionsReadyAPI Questions7.2KViews0likes6Comments[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.12 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.6KViews0likes4CommentsContent Message Assertion - better error message?
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 or junit report is very shallow. for example: ----------------- Messages ------------------------------ [Message Content Assertion] Message Content Assertion failed : failed/compared = 1/16 When getting such an error in automation it's very hard to understand what's the failure. I've tried to increase SoapUI log lever, but w/o any success to get better explanation. 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.1.1KViews0likes2CommentsRe: settings.xml in maven plugin
i've found out that i can use this line to update the settings. <settingsFile>${project.build.testOutputDirectory}/soapui/soapui-settings.xml</settingsFile> but is there a better way just to override some settings? all i want is to define the scripts folder, using the line above works fine but the settings.xml is too "big" and not so friendly for maintenance916Views0likes0Comments