The document provides guidelines for creating page objects that are DRY (Don't Repeat Yourself) when testing web applications. Page objects should provide an API of page actions without exposing web elements, initialize themselves, follow the builder pattern, and avoid duplication to keep code DRY. The document ends by inviting further discussion on page object best practices on the #selenium chat or via Twitter.

1. My Page Objects are
DRYer than yours.
Anthony Browness

2. Page Objects should:
 Provide an “API” of actions on the page
 Initialize themselves
 Not expose WebElements
 Mostly follow Builder Pattern
 Be DRY(Don’t Repeat Yourself)

3. The Status Quo

4. An equivalent Page Object

5. I’m getting thirsty,
let’s talk more!
 freenode #selenium
 D3M0S
 Twitter: @demos74dx