QA Journal — Entry 008
On why automation didn't take my job
Every few months, someone asks if automated testing means QA is going away. I always laugh, because the robots and I aren't doing the same job. Automation is brilliant at checking the things we already know to check — run these five hundred cases again, confirm nothing we understood yesterday broke today. But automation only ever tests what someone already thought of. The bugs that scare me are the ones nobody thought to write a test for yet.
Photo by Alex Knight on Unsplash
How a QA brain runs the check
Is this check stable and repetitive enough to be worth automating?
Am I automating to save real time, or to avoid having to think about it?
What can a machine confirm, and what still needs a suspicious human?
Does this test fail for the right reasons, or just every time the UI moves?
Who maintains the automation when the product changes underneath it?
What am I freeing myself up to explore by letting the robot handle the boring part?
WHY IT MATTERS
Automation guards the known; humans hunt the unknown 🟡
Automated tests are a safety net for everything we've already learned the hard way — they catch regressions so I don't re-check the same hundred things by hand every release. But a net only catches what falls into it. Exploratory, human testing is how we find the failures that were never in a test plan because nobody imagined them. The best setup isn't robots versus people; it's robots holding the floor steady so people can go look in the corners.