Also, as an alternative, is the 'clone' option on a your TestCase useful at all?
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! :-(
Hi Michael,
Sure, sounds frustrating, but open source products are here for us to improve :-)
I must admit I've never used the import/export functionality on a level less granular than project level (which I think worked fine last time I did it).
Maybe there's a problem exporting/importing TestCase's where there is a dependency on a more global object e.g. a service definition which is defined at project level? Its just a guess, but maybe only non-dependant TestSteps within the TestCase export fully? I haven't had time to try it, but I guess if you look in your exported TestCase.xml maybe there are details missing which mean your TestSteps don't get fully replicated on import?
Were there any error messages in any of the logs on import or export?
Regards,
Rup
Also, as an alternative, is the 'clone' option on a your TestCase useful at all?
I tried the Clone functionality. It works "somewhat". Meaning if I define a service with (a) method(s) with the same name(s) as those that the TestSuite being cloned refers to, it indeed creates a new testsuite containing copies of the test steps (and these even including headers, assertions, etc.), so that would almost fit my bill. I could live with the effort having to define those methods beforehand and having to select one for each step, although that's very tedious, too.
But - and that's big BUT: for some stupid reason it does not copy ALL parameters. My calls have about 10 parameters each. For some strange reason about 6 or 7 of these are copied over fine but 3 parameters are always missing.
The names are exactly the same so I don't get, why these values are not copied over, as well.
But just randomly copied values are almost as good or bad as none, since one then has to double check each and everyone. :-(
This is so infuriatingly buggy and intransparent!
Aaahh! Now I finally got it: the missing values are the same as the default values. One needs to specify the default values in the service definitions and then these values also appear in the test-steps!
OK - so, with that new wisdom I now finally have a way to somewhat reliably copy a test-suite from one project into another!
One has to manually create a service and method(s) in the target project - including the parameters and their default values.
Then one clones the test-suite from project A into project B and one needs to select and assign the right service and method for each test-step along the way.
Not exactly very elegant but still somewhat faster than recreating the test-suite(s) from scratch...
