Thank you for following up. Sadly, real drivers and xvfb are not available in the restrictions of my environment. I agree about GhostDriver, i have been looking for alternatives for several months. It's sad to me, since it got so far and then just died on the vine. I guess these things happen in OSS world. Rather than 25 people contributing effort to one robust project maturing project, we have 25 "somethingJS" projects, all of which are 85% the same, with 15% uniqueness. Maybe it's a healthy thing, but it doesn't feel that way from my point of view.
I was looking at jBrowserDriver just this week, and will be testing it next. Alternatively, I will try launching phantomjs using cli rather than the java library, since that will tell me the PID. Anyway, thanks for all your hard work on GEB, i'm sure i'll be using it eventually. If possible, try to think about the use case of constant web server monitoring in future design. It can already be used that way (for those who get around the driver problem). However, maybe there are things you might do differently in the future keeping the monitoring scenarios in mind. Maybe things that selenium doesn't do, because they don't generally seem to be aware of the monitoring use case either (despite the fact that new relic is built on selenium). Regards, Jerry Gerald R. Wiltse [email protected] On Thu, Feb 25, 2016 at 4:41 PM, Marcin Erdmann <[email protected]> wrote: > 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 >>> >> >> >
