Tester's Digest

A weekly source of software testing news


ISSUE #52 - March 31, 2018

Digging further into web UI testing, we focus on Selenium as a popular approach. Let’s look at some ways of making Selenium tests sane, starting with PageObject Model.

Topic: UI Testing with Selenium

The rest of resources here assume that you know what Selenium is, but in case you don’t, here is a refreshing look at a tester’s first experience with it:


Good old introduction to Page Object Model to create a layer of abstraction between your UI and the tests thereof:


Using PageObject and PageFactory patterns with Selenium:


Using the Robot pattern which to me seemed like a glorified PageObject model. It is well presented with examples targeting Android based testing.


Argument for using data- attributes to locate UI elements in your tests, so they can be independent of CSS and class name changes in the front end code.


How GitLab switched their UI tests from PhantomJS to headless Chrome with Selenium and ChromeDriver, covers differences between PhantomJS and Selenium in a lot of detail:


How to set up your Visual Studio Code IDE for debugging of Selenium WebDriverIO (Node.js based) tests, with niceties such as breakpoints:


People commonly advocate use of a BDD layer like Cucumber on top of your Selenium tests (and I had a good experience with that approach), but here is some well considered criticism, few years old yet still valid.



Suitable for April 1st, or for any other day if you’re bored of the regular “Lorem ipsum” text in UI mocks:


If you received this email directly then you’re already signed up, thanks! Else if this newsletter issue was forwarded to you and you’d like to get one weekly, then you can subscribe at http://testersdigest.mehras.net

If you come across content worth sharing, please send me a link at testersdigest@mehras.net