Driving Observability with Selenium Grid 4
Selenium Grid can be a bit daunting to get up and running. Starting it is quite easy, but using it effectively can require pulling in third-party tools. In this workshop we’ll cover how to run your grid effectively, using best practices culled from several large grid installations.
Outline/Structure of the Workshop
- Describe what the grid is intended to solve, then get into how it solves it
- Going deeper into the funnel, how does it get its instructions, and how does it pass them to the nodes?
- We’ll start with the conventional setup of hub and node servers running on the same box, for simplicity.
- Different options and flags that can be used when starting the hub/node processes
- What kinds of logging do the nodes/hubs do that can help in debugging and investigating problems?
- What is Docker?
- How do you setup standalone & grid:hub-node using docker?
- Using docker-compose to simplify docker grid setup process
- How do you run a test in a container?
- How do you run a test against the docker grid setup?
- How do you look at the logs of tests running in a container?
- How to build your own docker image with custom browser versions
- Creating a hybrid Selenium Grid (docker + a local IE/Safari node).
- Integrating Selenium Grid to the CI pipeline (Jenkins).
- Setting up a UI manager for all your docker installations
- How do you scale containers?
- Running tests in parallel against a scaled Selenium Grid
- Selenium Grid on Amazon ECS using ecs-selenium
- Overview of third-party tools
- What Selenium Grid is and are its capabilities
- How to run a grid
- How to scale nodes
- How to debug
- How to build your own docker images for custom browser requirements
Anyone who wants to learn about setting up, debugging, scaling and driving observability and with Selenium Grid 4
Prerequisites for Attendees
Knowledge of Selenium is a mandatory requirement, as the workshop will only focus on the Selenim Grid and won't cover how to write a script.
- This will include installing Hyper-V
- This will include installing the latest version of VirtualBox
Linux Distributions: https://docker.github.io/engine/installation/linux/
- The requirements will vary depending on the flavor of Linux being used
Selenium-server-jar (latest): https://bit.ly/327RZjR
Latest Selenium 4 version: 4.3.0.jar
You will also need the browser drivers and language bindings necessary for your target configuration, listed on this page: https://www.selenium.dev/downloads/
- If you intend to work with an auto-scaling Grid, an AWS account with full EC2 permissions.
- It is also recommended that you have Eclipse or IntelliJ, a GitHub account, and an open USB port so participants can share files using a thumb drive.
Tracing Selenium Grid
- Install Coursier via a homebrew `
brew install coursier/formulas/coursier`
- Install Jaeger via docker
schedule Submitted 4 months ago
People who liked this proposal, also liked:
Noemi Ferrera / Corina-Adina Pip / David Burns / Diego Molina / Jim Evans / Manoj Kumar / Marcus Merrell / Simon Stewart / Titus Fortner - Q & A with the Selenium Committer's PanelNoemi FerreraSDETAmazonCorina-Adina PipQA LeadDeloitte DigitalDavid BurnsHead of Open Source Program OfficeBrowserStackDiego MolinaStaff Software EngineerSauce LabsJim EvansContributorSelenium ProjectManoj KumarVP, Developer RelationsLambdaTestMarcus MerrellDirector of Technical ServicesSauce LabsSimon StewartProject LeadThe Selenium ProjectTitus FortnerSr. Solution ArchitectSauce Labs
schedule 4 months agoSold Out!
Q & A with the Selenium Committer's Panel moderated by Noemi Ferrara.
Mark Winteringham - What Exactly Do You Do in Test Automation?Mark WinteringhamOpsBossMinistry of Testing
schedule 4 months agoSold Out!
If you took the time to sit down to answer the question “what do you do as an Automator on a daily, weekly or monthly basis”, what would you come up with? Would it just be coding, coding and more coding or would your answers highlight a wide and wonderful range of activities you carry out?
For a skilled Automator, success relies on more than just being comfortable with programming languages and tools. It requires a diverse range of skills, techniques and experiences which the newly released Ministry of Testing automation curriculum has captured and organised in a way so that everyone can see the abilities an Automator has or can attain.
In this talk, Mark will share how his own experiences and the experiences of other automators have helped curate the Ministry of Testing automation curriculum. Through these stories, we’ll learn how the journey of an Automator is a varied one that can easily employ pen, paper and questions as much as IDEs, frameworks and libraries. We’ll also learn how an open source community curated curriculum can help you regardless of your abilities, role and context and how you can help it grow by sharing your own experience.