Leading test automation expert and engineering practices trainer from Alfa-Laboratory. I’m rocking QA-industry since 2012. Has passed all roles ranging from manual QA to QA Lead. I’ve been in IT since 2007, started as developer and system administrator. For 4 years I was involved in the testing of more than twenty projects, participated in the development of two test automation frameworks. I was engaged in an adoption of hybrid cloud infrastructure in Bank. My mission is spreading the culture of quality and DevOps.
Topic: Rubber cluster for dynamic selenium grid
Many of us have experienced such situations when projects involve +100500 automated tests and all these projects are subject to review more often than once in two weeks. And in the meantime, you don’t have an adequate amount of physical and monetary resources to build up a powerful farm.
Fast delivery of value to the customer will be out of the question if regression testing of each modification takes the entire sprint!
Nonetheless, even under these restricted conditions you can pipeline the tested artifacts through, spending not more than half an hour for the automated testing phase.
Now I will tell you how did we manage to bypass the dependency from the amount of test cases and obtain the automated testing results ASAP!
For this purpose we built a cluster using mesos+marathon. And containerization by means of docker in conjunction with the selenium grid made it possible to meet the challenge. We integrated automatic verification of automated testing results into the pipeline by employing self-written CLI-utilities and eliminated automated test launch conflicts/queues with the aid of jenkins cloud docker plugin, job dsl, serenity reports and other automation means, such as ansible.