From the course: Advanced Selenium: Page Objects and GUI Automation

Model your application for automation

From the course: Advanced Selenium: Page Objects and GUI Automation

Start my 1-month free trial

Model your application for automation

“

- [Alan] People often talk about page objects as a way of isolating their test code from maintenance when the application changes. Page objects are an abstraction layer, and there are many more abstraction layers that we can use. We can have abstraction layers for the infrastructure configuration to help us download and install dependencies. And all the way up to domain specific languages for writing the tests themselves. We need to understand all the options available and be able to decide between them to create the right abstraction at the right time. My name's Alan Richardson, and I've been automating applications to support testing since 1995, and I've worked with Selenium since 2007. I've written books on Selenium and Java, and I've coached many teams on how to improve their approach to automating their applications. In this course, we're going to look in depth at the many types of abstraction layers that we can create to support our automating. I'll explain the differences between functional and structural page objects, and we'll look at domain objects which can help us write code based domain specific languages, and we'll also have a quick look at Cucumber as a way of creating non-code based DSLs. If you want to understand how abstraction layers can go far beyond simple page objects, then this course is a good place to start.

Contents