Cloning assertions will fail when the response is different
I have a service with several methods that use different inputs to return the same data; example getAccountInfoByAccount, getAccountInfoByPhoneNumber, getAccountInfoByName etc. The response is alwa...
I understand that. What I wish SoapUI was capable of doing was to know what namespace it was declaring. That is where the issue lies. If you clone an assertions for 'Check for existence' from one call to another it will fail because the name of the request is different regardless of the response is an exact match across methods.
The attachment is meant to show the issue. Two different requests that return the same response. In this case a node named account. Their XSD is the same in this regard. So for example, in the first request getAccountByPhone. If I add a 'check for existence of account' by selecting a node in the Outline tab, right clicking 'for existence' it will add the assertion. Then in the assertion tab I click "Clone an arbitrary number of Assertions from this TestStep to other TestSteps" it will clone the assertion with the same declared namespace. When the TestStep is ran that includes this cloned assertion it will fail because the namespace declared does not match the operation. This requires the user to go through each request that is trying to use a cloned assertion and manually declare the namespace. If the user has to do this than there is no point in using the cloned assertion function to begin with.
