#selenium

well, im good with using a `nodejs` base, but seems like i have to install `java`, `selenium` and all that then

True?

is why i was looking to see if there was a base image with all of that already baked

Time to take a step back :)

So, you want to write your tests in JS?

I was going to say that

:)

Great mind, diemol-sl. Great minds

Correct. I currently have tests in `node.js`, using `package.json` to install `selenium-standalone` && atm `webdriver.io`.

So, the hub and nodes take the place of "selenium-standalone"

but, if i use a `Dockerfile` with a `nodejs` base it complains about `java`

So you won't need java on your nodejs image

so i take it i need something with `java` installed, or need to do that manualy

Selenium uses a network protocol to communicate with the selenium server (be it Hub, a standalone server, or something like chromedriver, geckodriver, or the IEDriverServer)

That's why you pass a URL to the remote webdriver instance. It's normally "http://localhost:4444/wd/hub", but it can basically be anything

one option is to run your tests, using a node base image, and then put them together in a docker-compose file with the docker-selenium images

Right

I have an example of that but with Java, in theory is to add “Script” at the end and that’s it :)

got it. so, i can’t use docker-compose, this will run on a kubernetes cluster

against an app in another container

well, not really, but you can get the idea

A kubernetes cluster is a little hardcore. You can just use docker-compose :)

well, thats the purpose of this, actually. the app exists already on a kubernetes cluster.

so im working on setting up some tests against it

Oh. Ok

You need one hub, and many nodes.

the cluster exists for lots of other reasons that i can’t change

The nodes should be configured to register with the hub

so, ideally, id just build a container w/selenium + my code in it && aim it at the running app & it would do its thing.

via IP address or whatever config

This looks useful to you: https://github.com/kubernetes/kubernetes/tree/m...

ah ok, so you want to have a deployment with only one container

Also: https://russell.ballestrini.net/selenium-grid-o...

right. at the moment i’m trying to take what i have running locally && just containerize it. dont care too much about kubernetes specifics yet

I'll let diemol-sl do the talking. He knows more than I do about this :)

would like to just use a `Dockerfile` && see if i can `docker run` it

oh, those are big words @simonstewart :O, I don’t think so

seems more than what i need to setup a hub + multiple nodes

but thanks :)

interesting

so yeah, with kube, you just have separate deployments for hub, ff, and chrome

I've not played with kubernetes yet. I should do that

so long as you name things accordingly (and they’re all in the same namespace), should be able to discover based on the internal dns

yeah, kube has been my muse for the past month or so

haven’t really tried to do webdriver stuff inside my cluster, though (i like mah saucelabs)

if you want to run those tests a bit faster, ideally you would need to deploy a Grid in k8s otherwise it is like deploying an app to run those tests sequentially

but one way to go is to use one of the standalone images, and add the needed stuff from node, then run the tests there

it could be a big image so the deployment can take some time

ok got it. i think that still might be larger scale that what I’m aiming to do. but, i may be thinking about it all wrong.

how many tests do you have?

locally i just `run serve cmd` for app in one terminal, switch and `run test command` in another && watch the tests run.

just a couple, this is `hello-world` prototype level atm.

so the idea is, we have an app running on a cluster, it gets updated occasionally. we want to roll out a standalone container that uses selenium to hit the web UI, ping a few things & verify its responsive, then shut down.

so we can regularly verify the web console runs

right

&& ensure an update doesn’t kill it for users

w/o having to manually hit it

so the tests could still be containerized and run as a k8s batch

maybe you can have a deployment with a grid and another container with your tests

yeah, that

there is a chart that may help you to simplify the grid deployment https://github.com/kubernetes/charts/tree/maste...

ok, looking up grid quick. still think its a lot bigger than what i need, but just a sec, thx!

hmm.

Yikes! It's not just docker any more. It's kubernetes and helm. What the heck is helm?

helm is life

(package manager; saves you from having to re-implement everything yourself)

so just for confirm, before going larger, as you can `FROM nodejs:latest` at the top of a `Dockerfile` to use a node.js base image, there isn’t an existing base image w/`java` and `selenium`?

standalone-server: http://goo.gl/Z4Z4aM Python: http://goo.gl/PXpx0Q IEDriverServer(32bit): http://bit.ly/1jik2D9 IEDriverServer(64bit): http://bit.ly/1lHYaTF

admin-sl is the idea just to run a few tests to monitor if the deployed app is ok?

meaning, i think we are running down the path too far, pretty sure i just need a base image so i dont need to `apt-get` all the java & everything.

diemol-sl yup. we want to just spin up 1 container, that has webdriver + selenium + our tests scripts, let it hit the web console in a headless browser & click test a few things.

so that can all be in one container, no prob.

in fact, that desirable. dont want to configure a bunch more bits to talk to each other.

ah ok, then I think you just need a container with Chrome, ChromeDriver and node installed

no need to install Java and the Selenium jar, with the Selenium bindings for JavaScript should be enough

yeah, i was expecting this list of base images https://github.com/SeleniumHQ/docker-selenium would have something more or less like that.

that i could `FROM` and be on my merry way.

I was thinking that, maybe to build containers only with the browser and the driver, and from there build up the other ones

right, if I have in my `package.json` as a dependency `"selenium-standalone": "^6.12.0"`

but I think I saw that somewhere, one moment

I think this guy has some images that can help you https://github.com/yukinying/chrome-headless-br...

I haven’t tried them myself, but this should work for your use case

oh nice, let me take a look at that.

def appreciate it.

any thoughts on ever providing an offical image for this use case? like, worth opening a github issue?

I had that idea, mainly to restructure how the images are built currently… you can open it and continue the discussion there :) maybe @ddavison has similar thoughts?

awesome ok will do

quite a convo - let me catch up on the context

ok - yea. admin-sl don't have your tests in the same container as selenium. If you want to build your own, that's fine - one thing you could do, is just share volumes. modify our images to include a customized test runner. have the test runner read some directory that is shared from your test container

created https://github.com/SeleniumHQ/docker-selenium/i...

ddavison-sl its not possible, or just not best practice?

generally i get you shouldn’t put multiple applications in one container, but in this case, the tests are tightly coupled to selenium

is why i ask

define tightly coupled, because as simonstewart pointed out earlier, you could just run your hub/nodes, then your tests just point to the URL

Well, `hub/nodes` doesn’t exist, in my current local setup. its just webdriver.io + selenium-standalone running against a local version of the web-app on `localhost`

which works, so since the webapp runs in production in a container, im just aiming to package up a 30 line test script + the dependencies into a container that we can deploy & run.

thats probably why i keep stepping back when i see hub + nodes, I think thats prob a lot larger than what I need for this use case

test

ack

Hey, does anyone know why all comments on selenium github issues are locked?

heh lost everyone. I must be totally off in my approach ,:)

nolski: you're probably looking at the old archive

are you talking about the google-code issues archive, nolski?

yuuuuuuuuuup

Sorry google brought me there. Are those relevant?

most shouldn't be

I'm having an issue with proxy auth in firefox not seeming to work https://github.com/SeleniumHQ/selenium-google-c...

if they were, they would have been transferred to the current issues

that issue was the best my google fu could get me

the selenium project used to be held within google code. we had used google issues a time ago (circa 2015). all issues were migrated to github, and they are locked. the current issues are at https://github.com/seleniumhq/selenium/issues

should I refile that under your new repo then?

Happy to write up a ticket :)

looks similar to this one https://github.com/SeleniumHQ/selenium/issues/1802

Dritz++

Yup that looks similar

ok - i get where you're going admin-sl - having just a simple standalone container that can run tests (like what you specified in the issue) this is an interesting use case.. let me brain dump for a sec

it's a cool idea because if a person wants to run one-off tests in a small docker container, just create the docker file, specify the FROM, add the RUN directive. cool. which languages would it support? if these images were to support any languages, they would be java or python, not js

and if there were multiple language binding supports, that'd be _n_ number of more docker images to maintain. don't like that