The document discusses evolving test automation frameworks by starting simply and solving problems over time through abstraction, separation of concerns, and domain-driven design. It advocates designing frameworks that are readable, maintainable, and unaffected by changes to the application or business rules through techniques like page objects, domain objects, and defining tests in terms of actors performing work.

1. Automation Frameworks
Don't Design, Let it Evolve
Anand Ramdeo
@testinggeek

2. Problem
Driven test automation framework

4. Sequential
execution
Not easy to
data drive
Firefox Plugin
easy to install
Record &
Playback
Easy execution
Help @ Hand
Export as
WebDriver Script
Excellent First Step
No Basic
Programming
constructs
Can not go
beyond pages
Crawling is
fun but we
don’t crawl
anymore

5. What happens when script is executed second time?

6. Guaranteed
Username
How would test respond to changes in GUI or business rules?

7. Readable
Maintainable
Difficult to Progress

8. Decoupling
Separation of concerns
Abstraction
Less friction, More
development

9. Page instead of elements
What if new fields are added?

10. One place to find
elements
Page Initializes
everything
Functions applicable
on elements are
exposed by page

11. Intelligent page objects
What if business decide to have multi page registration or
multiple welcome pages?

12. Test has no knowledge of physical implementation
What if business needs to capture more data?

13. Domain objects & workflow
What if there are different types of users and difference
channels of registration?

14. Actor
Performs Work
Check Results
Same steps over and over again

15. Randomization

16. Power of Abstraction
User.registersOnSite()
- Choose a random path to
reach at registration page.
- Generate random valid data
based on the business rules
for specific fields.
- Fill form in random order
- Choose a method to save
form or send data using http

17. Test is
• Readable and maintainable.
• Will not be affected by changes in the physical
implementation.
• Will not be affected by changes in the business rules.
• Can increase value of automation behind the scene
• Was evolved by solving one problem at a time.

18. Problem
Solved by performing
work
On some interface
App solves
the problem
Test proves
That problem is solved
App allows
actors to work
Test proves
that actor can
perform work

19. Value Enhancer

21. Anand Ramdeo
@testinggeek