Forum Discussion
Hi Rao
thanks for responding.
From your misc. suggestions I conclude that there is no easy way to have a multi-project workspace (one that contains multiple projects each having a series of mocks) and start the mocks contained in ONE of these projects without going through them manually.
That wouldn't be a big issue if one could start multiple instances of SOAP-UI but that's not so trivial, either. So we tend to have workspaces that contain multiple projects. And if more than one of them has an autoLoadScript interesting things can happen...
With the "design-flaw" I meant that when a LoadScript starts a series of mocks than there is NO visual clue (other than in the log-file) that any mocks were started and are running.
In our case this lead to the problem that someone had loaded TWO projects but hadn't even been aware that one of them contained a load-script that started mocks automatically.
So he manually started the mocks of the other project and - as since there was no indication that there were already mocks running from the first project (which happened to use the same port and partially also the same method names) - he was VERY surprised by the responses that his application got from "his" mocks. Their response matched NOTHING that had been defined in the mocks he had just started manually.
Had these mocks also created minimized windows (as mocks do when you manually start them minimized) it would have been obvious that there was already something running here (and one would also have a chance to stop these, which is also not possible with mocks auto-started by a load-script). So - as nice and convenient this feature is -it can lead to big confusion! Hope I could make myself clear...
Related Content
Recent Discussions
- 15 years ago