Hi,
ok.. thanks for your feedback. Our idea for this has initially been a "Run TestCase" teststep that could be used to invoke both internal and external TestCases. There are some twists to this that make it a bit tricky;
- UI updates; how should the UI behave when launching an external TestCase if you for example open that TestCases editor while it is running (I know its a bit far-fetched but it still needs to be handled..)
- LoadTesting; soapUI now creates internal copies of a TestCase for each running thread. This behaviour would have to propagate to referred TestSuites/TestCases as well. Also, how should referred TestCases be presented in the LoadTest Statistics Table/Diagrams? As one step or "expanded" as all contained steps?
- etc..
We'll have to ponder a bit.. one way to move forward is to dissallow LoadTesting for TestCases containing these kind of steps..
regards,
/Ole
eviware.com