Automation is Not

Some things to think about what QA Automation is

June 29, 2020 by cryan.com

Here we go...

Here are the eight things that people may think what QA Automation is - but they are so wrong:

A substitute for manual testing. It should complement the sum of all the testing done in a release cycle.
Easy. It takes time to build a strong test foundation that can be properly maintained.
Hard. There are a lot of "quick" hit automation tools. Make sure to have a plan. Don't create tests that just "chicken peck" functionality.
A One and Done. Automation requires lots of regular maintenance work for feature changes and to build in complexity.
Testing. It's only for verification of a specific predefined path. Just keep in mind that customers may not take the same approach - this is why manual testing is good.
One Size Fits All. There are lots of automation solutions available. In the past two companies I worked at, both decided to build their own - just so they could have ownership.
Just about Selenium. There are other alternatives available. Don't think you're limited to Selenium rules. Check out Katalon Studios, Robot Framework and CasperJS to name a few.
Abracadabra. It's not magical and worth QA time to understand the technology behind it so they can get the most out of it.

What do you think of my list? Did I miss anything? Or am I way off base?