Hi,
As you say, for Selenium 3.x, I seem to remember there being multiple dependency issues when I tried it.
In terms of Selenium 2.5, I seem to remember getting that working from a Groovy TestStep, at least on my Mac:
However, an alternative approach, which I ultimately found cleaner, is to run the Selenium script via an external Python script. It avoids any classpath / dependency issues - maybe see if this is an option for your case:
Regards,
Rupert
thanks for the response. It seems like a good idea to separate the jvms via the python script that then executes selenium. The downside is that you can not use the soapUI setup/teardown test suite scripts to do any real setup, since you are launching a new jvm each time
Hi,
Ok, thanks for the info. Not knowing your use case, I'm not sure what it is you need to setup or teardown that you can't do?
If there's a strong case for running Selenium 3.x directly inside SoapUI (please give maybe a brief example case, am interested), maybe submit a feature request for it:
https://community.smartbear.com/t5/SoapUI-Feature-Requests/idb-p/SoapUIFeatureRequests
I could maybe pick it up, I expect it will at least require some updates to some of the packaged dependencies and versions, maybe Java 8 - although I noticed a recent pull request in the SoapUI GitHub to enable it to be built against Java 8, so it might not be a bad time for those kind of updates.
Thanks,
Rupert
