This slide pack describes the challenges of We application test automation as well as provides a list of items that we would "prefer" to achieve when we automate. Finally, it provides an overview of a novel generative approach that cuts through the challenges, meets the "prefer" list items and allows Selenium-based test automation to be done at Agile speed.

1. Web Test Automation
PAGE OBJECT PATTERN FOR SELENIUM TESTS

2. Selenium-Based Test Automation
• Overview
• Page Objects
• Some ‘prefer’ items
• Some Challenges
• A new way
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]

3. Overview
• We need to assertively test web applications
• Web applications involve significant business workflows
• Web applications involve more rather than less pages
• Test automation is a project concern
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]

4. Page Objects
• Page Objects are a pattern for Page classes
• See: https://www.martinfowler.com/bliki/PageObject.html
• Each page in a targetWeb application requires a Page Object class
• Provide a clear separation of «page code» from «test code»
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]

5. Prefer Items
• When automatingWebApplication tests, we would prefer to:
• Maximise separation of «page code» from «test code»
• Maximise maintainability and scalability of test collections
• Attack challenging business workflow
• Do more rather than less testing
• Participate in Continuous Integration
• Participate in Agile projects (Stories,Tasks, Stand-Ups, Demo’s)
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]

6. Challenges
• When automatingWebApplication tests, the challenges are:
• Achieving, routinely, a strong separation of «page code» from «test code»
• Being able to routinely deal challenging business workflow
• Developing tests as well as Page Objects, with confidence
• Going for the «more rather than less» proposition
• Participate in Agile projects given the test dev. time/effort involved
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]

7. The New Way
Generation of Page Objects
• Pages
• Page ‘content’
Step 1
Definition
• Read Definition
• Write PO
Classes
Step 2
Generate • Write tests
• Use PO classes
Step 3Test
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]

8. Outcome
• With the new generational approach:
• Achieved -> a strong separation of «page code» from «test code»
• Achieved -> being able to routinely deal with challenging business workflow
• Achieved -> developing tests as well as Page Objects, with confidence
• Achieved -> going for the «more rather than less» proposition
• Achieved -> Able to participate fully inAgile projects
• Achieved -> maintainable, scalable and accessible test automation codebase
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]

9. Definition File
This definition file is for the
hypothetical testing of
Lufthansa.com.This site is public
and doesn’t like Roots 
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]

10. Generation
This shows the generation of the
Page Object classes. Some page
definitions are “empty” so don’t
have output. For real tests there
would be many more Pages.
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]

11. Write Tests
This shows the a fragment of a test
which uses the generated Page
Objects.This test asserts the
existence and associated content of
the Main Page footer items.
(c) 2017 David Harrison All Rights Reserved [https://dharrisonch.com]