| SmartBear Support wrote: |
|---|
Hi,
Can you upgrade to SoapUI Pro 4.6.1 and see if you see the same problem?
There have been improvements with REST testing with 4.6.1.
Regards,
Marcus
SmartBear Support |
Took me a while, but I see the same thing still in 4.6.2.
I cannot figure out how to replicate this consistently, I wonder if it is related to any instance when I may have run that particular call and could not reach the server or something, because it certainly doesnt happen too often... But here is some recently added entries from one of my service.xmls. Note they are identical and definitely added 'automatically' - I did not manually update the responses for that call.
<con:representation type="RESPONSE">
<con:mediaType xsi:nil="true"/>
<con:status>0</con:status>
<con:params/>
<con:element>data</con:element>
</con:representation>
<con:representation type="RESPONSE">
<con:mediaType xsi:nil="true"/>
<con:status>0</con:status>
<con:params/>
<con:element>data</con:element>
</con:representation>
