~/talk

Selenium Grid Docker Containers, Selene and pytest

Talkat SeleniumConf Chicago 2018 · 2018-10-18..10-19· [devops-and-delivery, testing]
slides:none on file

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

  1. 0:00Start
  2. 2:27install browser drivers on your system
  3. 3:00run your selenium test on your computer
  4. 3:25install selenium
  5. 6:11request a browser from the selenium grid process
  6. 9:02collecting test cases
  7. 20:45ask for a remote web browser by using web webdriver
  8. 21:40interact with the web browser
  9. 25:51set this up in continuous integration
  10. 27:25split them up into small test groups
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.