Selenium Grid Docker Containers, Selene and pytest
summary
A reproducible Selenium test stack runs from three shell targets: make test env up, make test, make test env down. It uses Selenium Grid Docker images for hub/node browsers, a dockerized test-runner with Selene and pytest, and produces results.xml plus stdout logs and screenshots on failure. VNC-enabled debug images and a show_node helper let developers interact and pdb into tests. The same commands run in Jenkins, with junit reporting and optional pytest-testgroups for cheap parallelization.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:27install browser drivers on your system
- 3:00run your selenium test on your computer
- 3:25install selenium
- 6:11request a browser from the selenium grid process
- 9:02collecting test cases
- 20:45ask for a remote web browser by using web webdriver
- 21:40interact with the web browser
- 25:51set this up in continuous integration
- 27:25split them up into small test groups
related talks
25mEfficiency Matters: Mastering Dockerized Scalable Grid for UI Tests
43mSelenoid: running Selenium tests in Docker containers
06m"Selenium 4.0 Grid Observability, Setup & Execution"
44mZalenium: Use A Disposable And Flexible Selenium Grid Infrastructure
45mRubber Cluster for Dynamic Selenium Grid (Opening Keynote)
47mWeb and Mobile testing with Selenium, JUnit 5, and Docker
34mSelenium 2 Grid
28mAppium meets Selenium and Docker
