Update definition removes the old web methods
Hi: I am using the latest 2.0.2 Pro, dist-286 verision of SoapUI. There is a problem with "Update Definition." Let's say I have a web method called "LinkCEDevice" in my definition "DeviceManageme...
Forum Discussion
Hi:
1. Refactor only shows me the mapping between LinkCEDevice and LinkDevice VISUALLY/GRAPHICALLY. However, after I finish the refactoring process, it displays "update is complete" or something like that. It doesn't actually go into any test cases to update the methods. In this case, it doesn't REPLACE LinkCEDevice with LinkDevice physically. What I am trying to say is the refactoring only shows us the graphical mapping rather than actually replacing the old methods with the new methods. Therefore, I think this is a bug in refactoring.
2. Update definition doesn't replace LinkCEDevice with LinkDevice either. It simply removes the old method from all test cases, leaving us to find out where we should insert the new method.
Li
1. Refactor only shows me the mapping between LinkCEDevice and LinkDevice VISUALLY/GRAPHICALLY. However, after I finish the refactoring process, it displays "update is complete" or something like that. It doesn't actually go into any test cases to update the methods. In this case, it doesn't REPLACE LinkCEDevice with LinkDevice physically. What I am trying to say is the refactoring only shows us the graphical mapping rather than actually replacing the old methods with the new methods. Therefore, I think this is a bug in refactoring.
2. Update definition doesn't replace LinkCEDevice with LinkDevice either. It simply removes the old method from all test cases, leaving us to find out where we should insert the new method.
Li
