Selenium with Kubernetes or Docker Swarm or AWS ECS

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Selenium with Kubernetes or Docker Swarm or AWS ECS

Erick K
I have been tasked to work with our QA team in setting up Selenium to automate testing.

The QA team would like to have a Jenkins job that launches Selenium testing after the current build. 

The idea is to have Jenkins initiate the launch of Kubernetes with Selenium nodes to do the testing. 

Is anyone in the community using Selenium in this way or with either Docker Swarm or ECS because I'm somewhat confused. 

Thank you!

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/f97037c0-34ad-4ea0-82ab-02142b7d7175%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Selenium with Kubernetes or Docker Swarm or AWS ECS

Krishnan Mahadevan
Erick,


Maybe you can take a look at that.

But if your use case is just to setup a selenium execution environment for your QA team, you could consider the following:
  1. https://github.com/zalando/zalenium
  2. https://github.com/RationaleEmotions/just-ask (This is created by me)
The above two solutions basically work in almost in a similar model (wherein the Grid size upscales and downscales depending on the load), but involves at-least the hub being spun off separately. Maybe you could have your Jenkins job spin off the Hub as a pre-execution step before the tests run and have a post execution step which terminates the hub.

Depending on your test script volume you can decide which route you would like to take. 

Also there are selenium grid jenkins plugin itself which basically transforms your currently available Jenkins cluster into a Grid farm as well.


I am not sure if spinning off Kubernetes by a Jenkins job is a good idea. Ideally speaking you might want to have a K8 cluster up and running and then work with the k8 APIs to upscale or downscale your nodes.

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/
My Technical Scribblings @ http://rationaleemotions.wordpress.com/

On Tue, Jul 10, 2018 at 4:39 PM, Erick K <[hidden email]> wrote:
I have been tasked to work with our QA team in setting up Selenium to automate testing.

The QA team would like to have a Jenkins job that launches Selenium testing after the current build. 

The idea is to have Jenkins initiate the launch of Kubernetes with Selenium nodes to do the testing. 

Is anyone in the community using Selenium in this way or with either Docker Swarm or ECS because I'm somewhat confused. 

Thank you!

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/f97037c0-34ad-4ea0-82ab-02142b7d7175%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/CANikZLnBjeEcFB%3DNRp%2BdBnTO3gQfOQwDbXWkjcSWjX_OLNLrgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.