Forum Discussion

nmrao's avatar
nmrao
Champion Level 3
9 years ago
The reason is simple. It is because, the http header 'Content-Tye' is not coming as expected i.e., 'application/json; charset=UTF-8'
  • piyu_sarda's avatar
    piyu_sarda
    Occasional Contributor
    9 years ago

    Hi Rao,

     

    In the application I am going to automate will contain the collection json as the content type. Also if you notice in the screenshot the JSON is picked up properly and shown under JSON tab, so the response is processed properly. In the JSON response i have attached, there is an empty line at the top. If I remove that, it all works properly with the same content type and does not throw an error on property transfer. 

     

    There should be an option in SOAP UI to process the response by stripping the empty spaces before and after the JSON as it can be done with the request. It should not restrict the downstream components for the empty spaces.

     

    Could you please check this?

     

    Thanks,

    Piyu

    • nmrao's avatar
      nmrao
      Champion Level 3
      9 years ago
      1. If that is case, have you checked with the concerned developer to find why an empty line is coming in the response which I believe is the right way to address the problem as that is making the response invalid.

      2. Of course, you can handle such response in soapUI as well, but treat this as only making a workaround. To do that, you can have a script assertion, so that it won't affect your existing test steps as well.
      • piyu_sarda's avatar
        piyu_sarda
        Occasional Contributor
        9 years ago

        Hi Rao,

         

        I have checked with the developer and the APIs are being widely used by various applications with the empty line at the top for a number of releases now and no other delivery teams have reported this issue. So I believe, using other frameworks this is not an issue otherwise would have been flagged high time. Therefore convincing and getting this changed from dev will not be possible.

         

        In Soap UI also, the proper JSON is picked up and shown on JSON tab of response but unfortunately cannot be processed on property transfer. I think SOAP UI uses raw response for property transfer rather than JSON which is picked up.

         

        I have even  tried script assertion and that also throws the same error.

         

        I will be surprised if we dont have a solution for this in SOAP UI and had to unfortunately move to other tool for this automation. :(

         

        Regards,

        Piyu