This document discusses using robot handles in test automation code to reduce code changes when the UI changes. Robot handles abstract away UI elements so that test code only needs to change the handle implementation when the UI changes, rather than changing every test. This improves maintainability by following the single responsibility principle where the test code focuses only on verifying scenarios and the handle code focuses only on accessing the UI elements. Examples of using robot handles in test code are provided.

1. Robot Handles
Andy Palmer
Giving Selenium a Helping Hand

2. Why does test code change?
• What you do in a scenario changes
• How you do it in the UI changes
Single Responsibility Principle says that a class
should have only one reason to change

3. Why should test code change?
• What you do in a scenario changes
• How you do it in the UI changes
Single Responsibility Principle says that a class
should have only one reason to change

4. Let’s look at some code

5. @AndyPalmer
andy@riverglide.com
http://github.com/RiverGlide/robot_handles_example