Test Automation Framework (Selenium with Java) — Zeitgeist or Page Loading Strategies and Waits

Tomasz Buga
9 min readNov 20, 2021

S01E06 of the Test Automation Framework series about everything you’ll need to set up the nice, simple, yet sophisticated framework.

Covered with clear explanations and pretty illustrations.

Sounds like fun? Cool. Now, please, fasten your seatbelts because you’re here for a ride.

S01E01 — What To Automate?

S01E02 — Test Automation Environment and Tools

S01E03 — The First Selenium Test Case

S01E04 — Selenium Foundations Revisited

S01E05 — Page Factory and Elements Related Exceptions

S01E07 — Translating JIRA with Selenide (with Exercises)

S01E08 — JIRA, Selenide, Complex SQL, Java Objects with Equals & HashCode (with Exercises)

S01E09 — Code Review and Refactoring (Part 1)

S01E10 — Code Review and Refactoring (Part 2)

S01E11 — Allure in Action

A couple of days ago I’ve received an email from the Ultimate QA, as I’ve been using one of their mock pages to fulfill a recruitment task for one of the companies I’ve been applying to a few months back.

The subject stated “Implicit vs Explicit waits??”. The email itself contained a short comparison of both Implicit and Explicit waits with three bullet points per type. There was more material on the topic available in the blog post (from 2016). It contains a decent explanation of the issues that comes with waits, but eventually, it doesn't cover much more than any other article available on the web. Nevertheless, I am grateful for that email, because it struck me with a fact that I know nothing about waits in Selenium.

Shortly after – I’ve begun my research on the topic.



Tomasz Buga

Software Development Engineer in Tests. Passionate about programming. Experienced, former employee of the insurance industry. Graphic designer by choice.