Hey
Jagruuti,
I've had this several times myself.
What i do when i get this scenario, is that i grab the RAW request from ReadyAPI! and grab the RAW request from Postman and compare the two against each other....payload, http headers, full url string (servername and URI) etc.....that'll enable you to identify what the issue is.
I like the Fiddler app for this sort of diagnostic analysis (it proxies the requests/responses), but it's not essential, but its a great tool that'll help with other issues where you need to compare between Postman and ReadyAPI!/SoapUI.
Oh, btw. Regarding the image you attached. You scribbled out a lot of stuff you dont actually need to. You dont need to scribble out stuff like teststep names to ensure youre covering off the security aspects. For future reference you need to blank out the 'servername' (NOT the URI....just the host/servername) and any authorisation/authentication details like usernames and passwords/token details, etc. If you consider the details a black hat would need to cause problems (i.e. the servername and auth details) that should guide you in determining what needs to be blanked/scribbled out. Without these details (host/servername and auth details) someone with nefarious intentions would have no place to start.
Ok, thats all i got for now!
Nice one,
Rich
