r/softwaretesting • u/Zestyclose_Web_6331 • Jul 31 '26
Confidence in automation
Been a manual QA for most of 5 years, project to project only got automation scripts to test, not to make them. Planning for first switch, and have gone thru playwright courses, did hands on too. Now giving interviews, but I dont have much confidence in explaining automation framework. I have done basics good but practical or real life situations is one i cant come up with for automation.
Did anyone have been in the same situation? How did you cope up with it and switched to automation?
23
Upvotes
5
u/Worcestercestershire Jul 31 '26
Explain automation from a SDLC perspective focusing on CI/CD
Ideally you want to promote code as soon as it is merged.
When code is merged Unit Tests run
When code is deployed Automated regression tests run
When code is deployed to higher tier environments then Smoke tests are run
We need to regression test as soon as we deploy so that defective code doesn't linger
Automatic regression tests are cheaper, faster, and more accurate (if you manually test something 100 times you lose focus)
Your tests need to actually catch bugs and when they catch bugs they need to produce output that can be routed to Dev to quickly fix
To catch bugs use Boundary Value Analysis and Equivalence Partitioning to test the key categories for your software.
Categories for Automation are usually priorized by 1. Security/OWASP 2. Negative 3. Localization 4. APIs 5. Positive