So these are the basic steps an automation tool does:<\/p>\n
Wait, Find, Action – Repeat..<\/p>\n
(Still thinking \/ exploring a cool name for this)<\/p>\n
“Wait”\u00a0 for the AUT and automation tool to be in sync, and the object loaded and ready to interact with<\/p>\n
“Find”\u00a0 OnLy the ‘Desired’ object “ALWAYS”<\/p>\n
“Action”\u00a0 should be compatible with supported browsers \/ environments and handling the usual errors (delete previous text in text field etc.)<\/p>\n
What I really wanted to talk about today were delays (wait). I hope most people reading know this, but it’s too important so I’ll repeat<\/p>\n
First we established how important delays are, there 1\/3rd of the whole automation! (in a way)<\/p>\n
Second, here are my “object delay rules”:<\/p>\n
1. Have a delay BEFORE interacting with ANY object “ALWAYS”<\/p>\n
2. NEVER use a static delay, ALWAYS a dynamic delay<\/p>\n
3. Check for not just if the object is visible, is it READY to interact with? *<\/p>\n
If you do these three things with delays, you should be fine<\/p>\n
* Exceptions are always there, but they should be the “exception”..<\/p>\n
#QsDaily<\/b>\u00a0#AutomationFrameworkDesign<\/b>\u00a0#TestAutomation<\/b><\/p>\n<\/div>