![Automation stories – Framework Debug lessons [TechBeacon Article]](https://media.licdn.com/dms/image/v2/C5112AQFoNrNUFsJsLg/article-cover_image-shrink_600_2000/article-cover_image-shrink_600_2000/0/1527259913458?e=2147483647&v=beta&t=w7rLtIyjgmfPN1EYmCdhlbyiFhhqvy-hjZHfR7koGeM)
Automation stories – Framework Debug lessons [TechBeacon Article]
Ali Khalid
![Ali Khalid]()
Ali Khalid
Heading Data Quality @ Emirates Airline | Transforming Analytics | Award winning speaker
This one time,
when we spent months finding the root cause of an alert problem,
Turned out windows 7 on a VM running chrome ran a bit wonky,
It was so cool we wasted months on such a silly issue.
But you know, in automation this is a
In the end here’s what we learned:
- Event handlers are important to deal with typical UI issues. “Anything that can go wrong will go wrong”, so prepare for it
- Even with the precautions you take, best to have a back-up plan.
- Keep the AUT and automation tool aligned
- When analyzing a problem, define and keep changing the variables to find a pattern
- We make the wrong assumptions all the time, it’s good to question them when you’re stuck
- And lastly:
The complete story can be read here in this TechBeacon article I wrote.
?
Any automation framework problems you’d like to share?
a Techie | QA | Sharing is Caring | Sharing the Tech Stuff
6 年Amazing
Principal Consultant-Trainer
6 年Ali Khalid, is this your article? Great points; however, there are some that I tend to disagree. Agree that unexplained errors can be a common occurrence during framework design. However, the proposed solution of learning to solve them quickly isn't the best approach, if you ask me. I tend to take a step back, often ending up ''changing' the problem itself, or look from a different point of view, pull out smaller units and solve them, or look for alternatives - any of these or a combination thereof. It has always worked for me. Getting stuck to a problem, so much so that your vision is blinded and can't see beyond, is the real problem!