Test Automation Strategy Questions

Evaluate which tests to automate and which to execute manually by weighing technical, business, and maintenance factors. Key criteria include test frequency and repeatability because tests that run often yield more return on automation; feature and user interface stability because unstable targets increase maintenance cost; test complexity and determinism because highly variable or flaky tests are poor automation candidates; and risk and criticality because high risk paths and release blocking checks may justify automation even if costly. Good candidates for automation include regression suites that run on every build, stable API and backend checks, data validation, performance and load tests, cross browser smoke checks, and repetitive high volume scenarios. Poor candidates include exploratory testing, new or rapidly changing features, one time checks, highly visual user interface interactions that change frequently, and tests that require extensive human judgment. Practical considerations include the initial implementation effort, ongoing maintenance cost, test data and environment setup complexity, tooling and infrastructure availability, and measurable return on investment such as time saved per run and reduction in escape defects. For interviews, explain a decision framework that balances value and effort, describe examples of tests you would automate versus leave manual, and show awareness of strategies to reduce flakiness and maintenance such as modular test design, reliable selectors, and regular review of the automated suite.