On Wed, 8 Feb 2012 15:11:16 -0500
Lars Nordin <[email protected]> wrote:
> I've setup a small number of systems to run Selenium servers headless
> and didn't had much problems. This was some time ago using selenium
> 1.0b and Xvfb and not via Jenkins.
Heh. Yeah, not using Jenkins makes things a bit less opaque.
>
> Can you split the problem, into what is going with Jenkins and what
> is going on with Selenium?
Running selenium and driving the tests outside of Jenkins is no
problem, no.
>
> Is there some sort of log from the Selenium scripting as to what is
> going on?
Nothing useful shows in the logs.
> To understand what is going on with the browser, configure
> Xvfb to use a framebuffer ("-fbdir file") and then use xwd to see
> snapshots of what the browser is doing. It could be that the browser
> is taking too long to start, go to a certain page, SSL cert issue,
> etc.
Indeed. The basic problem is when selenium-grid in Jenkins works, it
just works. When it doesn't work, what should be irrelevant actions
seem to make it work. Like, hitting "enter" in a shell as Jenkins user.
This shouldn't make a difference, but it does.
However, at this point, I have a system in state that is working on
boot, so unless that changes, I'm hoping I'm done with attempts
to set it up... except that slave nodes will have to be set up as well,
so still searching for the canonical method that "just works".
>
> For the Jenkins, side what the build job running selenium say (i.e.
> Console Output from the build)?
When it fails, I just get the same error as if there is no framebuffer
configured at all.
>
> Another option is to dedicate a VM to run the browser and selenium
> server and leave it at that - then you can watch what is going on.
Yeah... all these VMs I have to poke at are headless.
Thanks for the feedback!
Cheers,
--
Michael Higgins
QA Intern, PuppetLabs
[email protected]
