I´ve several singleton instances in my API that get called via a "Groovy Teststep".
When executing a Groovy Teststep it seems, that no new VM is started - the objects "live" in the VM of the soapUI instance. That leads to several problems, when restarting a Teststep after changing external resources (files, database values and so on....)
=> is it possible to start a own VM each time I execute a teststep or a testcase?
Re: Singletons stay alive until soapUI is restarted
thanks for this, as you have noticed it isn't currently possible. Running scripts in a seperate jvm/process would impose quite alot of overhead I guess, and wouldn't give you access to the soapUI objects, etc.. but I'll put it in our JIRA for improvements..