Forum Discussion

richie's avatar
richie
Community Hero
7 years ago

Works in Postman but not SoapUI? Exception: Cannot get property 'testCase' on null object

Hi,   UPDATED MESSAGE.   I have a REST request publishing a flat file record to a service and I'm getting an authentication error when I submit the request via SoapUI, but no error response when ...
  • Nastya_Khovrina's avatar
    Nastya_Khovrina
    7 years ago

    Hi Richie,

     

    Thank you for your post and for the provided details. 

     

    I see that the Content-Type header differs in your requests. Maybe, you need to change the Media Type value in ReadyAPI to 'application/x-www-form-urlencoded'.

     

    But, according to the screenshot and status 401, the issue is related to the authorization. You can try to manually add the Authorization header to ReadyAPI, copy the value from the Postman and send a request.

     

    Also, to determine the cause of the issue, we need to compare full raw requests from ReadyAPI and from Postman. 

    To get a raw request which was sent from a browser (or from another application) you can use Fiddler (http://www.telerik.com/download/fiddler) which is a free tool to capture HTTP(S) traffic.

     

    As for the issue in the logs, please check the Event Handlers for your request: https://support.smartbear.com/readyapi/docs/testing/handling-events.html

Nastya_Khovrina's avatar
Nastya_Khovrina
SmartBear Alumni (Retired)

Hi Richie,

 

Thank you for your post and for the provided details. 

 

I see that the Content-Type header differs in your requests. Maybe, you need to change the Media Type value in ReadyAPI to 'application/x-www-form-urlencoded'.

 

But, according to the screenshot and status 401, the issue is related to the authorization. You can try to manually add the Authorization header to ReadyAPI, copy the value from the Postman and send a request.

 

Also, to determine the cause of the issue, we need to compare full raw requests from ReadyAPI and from Postman. 

To get a raw request which was sent from a browser (or from another application) you can use Fiddler (http://www.telerik.com/download/fiddler) which is a free tool to capture HTTP(S) traffic.

 

As for the issue in the logs, please check the Event Handlers for your request: https://support.smartbear.com/readyapi/docs/testing/handling-events.html

richie's avatar
richie
Community Hero
7 years ago

adding the authorization header in (despite it already being present in the request) fixed the problem!

 

Thanks so much!

 

richie