Tried to address one the common issues faced by new automation testers in this link: Exception when clicking on an element
Exception when clicking an element, Unable to find a element, Can’t find the locator, Unable to find the locator value – Generally, all these exceptions can be handled by implementing anyone of the below solutions.
Check your locator value again
Use different locator to identify the web element
Your driver might be trying to find the element before it is ready, so use appropriate waits
Totally new to this challenge (as I’ve transitioned to QA Automation since last year) and have found so many new and exciting opportunities. I’m kind of fast-tracking my progress, knocking out “days” in small batches due to limited bandwidth and what-not. The best, funnest things I’ve come to love about my engineering role is the challenge of always learning something new, on-the-fly.
I’m still working through PYTHON as it was the language I have been teaching myself. But I’ve been exposed to proprietary frameworks, custom frameworks, and most recently KATALON - a superb out-of-the-box framework that has surpassed a lot of testing issue I’ve had with others. And lord knows, I’ve researched just about all the best ones.
In conclusion, for the next 30 days, I will be consistently active in posting my findings here … as well as on my blog which I will only promote this one time - http://severeqa.blogspot.com/. This was dedicated primarily to QA, as a round-table to discuss things not-always about testing, but has since shifted to Information / Cybersecurity – my passion.