Gerald, Geb is a wrapper around Selenium so if you have issues with the WebDriver implementation you're using then unfortunately there isn't much that Geb can do for you.
I would advise against using GhostDriver given that it is unmaintained at the moment: https://github.com/detro/ghostdriver#help-needed. I found that using a real browser like Firefox or Chrome and running it on a headless server in a virtual display (Xvfb) is way more reliable than using headless drivers. This is for example the setup I'm using to run functional tests in SnapCI on my current project. I have never tried using jBrowserDriver though, maybe it's worth trying out: https://github.com/MachinePublishers/jBrowserDriver. Feels like it's worth trying to run Geb's suite using it - https://github.com/geb/issues/issues/426. Marcin On Tue, Feb 23, 2016 at 1:17 PM, Gerald Wiltse <[email protected]> wrote: > Marcin, > > I've been using selenium and phantomjs/ghostdriver in Groovy to do > headless monitoring of a web application for a while now. We'll probably > switch to GEB, but our biggest issue is that PhantomJS keeps leaving hung > processes due to unknown conditions, and because we cannot retrieve the PID > of the phantomJS process upon instantiation, we don't have an effective way > to forcibly terminate it. Based on your experience, do you think it's > possible to solve our issue under GEB? > > Gerald R. Wiltse > [email protected] > > > On Mon, Feb 22, 2016 at 4:42 PM, Marcin Erdmann <[email protected] > > wrote: > >> Version 0.13.1 of Geb is now available from Maven Central. >> >> The 0.13.1 version is released to address a regression discovered in the >> 0.13.0 release (https://github.com/geb/issues/issues/422) as well as two >> concurrency related issues (https://github.com/geb/issues/issues/421, >> https://github.com/geb/issues/issues/423). >> >> Thanks, >> Marcin >> > >
