Forum Discussion
Hi Michael,
Does seem like a reasonable functional improvement.
My quick thoughts are:
- (short term hack) As you say manipulating the project XML file is an approach, I've done this before for smaller tasks. It should definitely work, but always work on a back-up of course!
- (medium term) There will probably be a Groovy script approach to cloning the objects involved. Whilst this would probably be a repeatable solution that you could share, it would probably be a reasonable effort. I once did a Groovy script to propagate changes in a service definition to all POST TestSteps in all TestSuites and TestCases, it wasn't too bad.
- (long term) Maybe fill out a SoapUI feature request (https://community.smartbear.com/t5/SoapUI-Feature-Requests/idb-p/SoapUIFeatureRequests) - then wait for someone to pick it up (could be slow, but does happen, I coded a simple one recently).
Regards,
Rupert
Hi Rupert
thanks for responding. I will fill out that request for sure!
Meanwhile I tried to experiment with the export/import features of soapUI but these don't seem to work at all!
I exported a test-case from project A. Then - in project B - I defined a service containing a resource containing a method with all the same parameters - ALL with the exact same names as the ones in project A.
Then I imported the previously exported test-case.xml into project B into a specific TestSuite.
I get popups re. some missing REST resource for each test-step and I select the above created resource for each (since all test steps in this sample refer to the same method). At the end I have the same number of test steps (i.e. the names of the test-steps made it over) but when double clicking onto any of the test steps nothing happens (right-click => OpenEditor: same result: nada), i.e. these imported test-steps all seem to be empty or faulty.
So, except the names of the test steps apparently NOTHING was imported and whatever got imported is useless.
This is a joke! :-(