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 ...
Forum Discussion
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.
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.