Three steps to click a button
▻https://hackernoon.com/three-steps-to-click-a-button-2098f42732f5?source=rss----3a8144eabfe3---
Photo by James Sutton on UnsplashI’ve been helping with test automation for a couple of projects. Every time we start fresh and have all good intentions to keep our regression suite clean. Every time we end up tossing things around and spending the time to adjust our scripts in order to avoid big changes with every little new UI change. Is there an option to reduce the overhead? I know my specs are a representation of original requirements. I also noticed that there is something usability engineers could benefit.I’ve spent some time analyzing what levels of abstraction we have during automating specifications. I looked at what type of language we use on each of these levels and this is what I found:A level of use cases. Where business processes and actors are defined;A level of screens and (...)