When you start to write automation for your projects you quickly realise that you need to organise and design the code. You will write far more than 'test' code, you also write abstraction code because you want to make 'tests' easier to read and maintain.
But how do you design all this code? How do you organise and structure it? Should you use a Domain Specific Language? Should you go Keyword Driven or use Gherkin? Should you use Page Objects with POJO or Factories? Do you create DOM Level abstractions? Where do Domain Models fit in?
In this session Alan Richardson will provide an overview of some options available to you when modeling abstraction layers. Based on experience of using many approaches, on real-world commercial projects, Alan will help you understand how to think about the modeling of abstraction layers. And in a talk illustrated with code examples, Alan will show you a variety of approaches and discuss the pros and cons associated with them.