Yelena
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: ReadyAPI 2.5 - Content assertions with values that contain single quotes are always failing
Sorry, I am not sure how to send a link for my case. But my Case #00314272. The last communication was that while they recommend updating your assertions, they recognize that "Select from Current" is not escaping quotes, so it generates incorrect assertion. And they are looking into it. I am surprised as well at the suggested resolution - update assertions to have it working in the newer version of ReadyAPI. Sounds more like a bug than a feature to me personally. I have rolled back to 2.3 for now.3.8KViews0likes3CommentsRe: ReadyAPI 2.5 - Content assertions with values that contain single quotes are always failing
update from our developers: "It seems that in ReadyAPI 2.5.0, the Expected Result is now parsed as a JSON object, so in order to use special characters such as quotes, they will need to be escaped if they are part of a string value. That said, please change your Expected Result to the following and let me know if that works for you: \'yourValue\'."3.9KViews0likes5CommentsReadyAPI 2.5 - Content assertions with values that contain single quotes are always failing
After upgrade to 2.5 all my assertions that had values with single quotes are always failing. I tried the following with no luck: - recreating the assertion - get value from the test (was thinking maybe there are some invisible characters or spaces) Assertion is failing with the message: -> Comparison failed. Path: [my path (JSON)]; Expected value: [my 'value' not found]; Actual value: [my 'value' not found]. P.S. Using wildcard to remove single quotes is the only thing that works as a workaround.Solved4KViews0likes9CommentsRe: Form Editor - Error Initializing Editor from Message
Ran into this old thread trying to find why I am getting the same message. After going over my request's raw XML noticed I accidentally removed opening bracket for one of the elements. So in my case, the error was caused by malformed XML & resolved by fixing syntax.2.7KViews0likes0CommentsRe: \r added to each line of the request
Thank you for the reply, Tanya. I did upgrade to 5.2 and still having the same issue. Oddly enough, the tests run fine with \r using SoapUI5.2 free version but SoapUI Pro displays malformatted XML error if I try to open my project. And I have to manually delete all \r's to be able to run it.5.3KViews0likes0Comments