Forum Discussion

Yelena's avatar
Yelena
Occasional Contributor
7 years ago

ReadyAPI 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 (wa...
  • Yelena's avatar
    Yelena
    7 years ago

    I opened a support ticket with Smartbear and they were able to reproduce the issue. It was forwarded to R&D team.

     

  • Yelena's avatar
    Yelena
    7 years ago

    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\'."

     

     

Yelena's avatar
Yelena
Occasional Contributor

I opened a support ticket with Smartbear and they were able to reproduce the issue. It was forwarded to R&D team.

 

Yelena's avatar
Yelena
Occasional Contributor
7 years ago

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\'."

 

 

  • Flo's avatar
    Flo
    Contributor
    7 years ago

    So they are asking to change assertion because of a minor update of ReadyAPI ... Hum I am surprised.

    Do you have the link to your support request please ?

    Flo.

    • Yelena's avatar
      Yelena
      Occasional Contributor
      7 years ago

      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.

       

      • richie's avatar
        richie
        Community Hero
        7 years ago

        Hi,

         

        I've been reading about json reserved characters today (due to a different post) - a single quote is not one of the json reserved chars and hence should NOT need escaping!?????

         

        see the link from stackoverflow

         

        cheers,

         

        rich