Manual and Automation Testing Interview Q&A - Product Based Companies
Manual Testing Questions:
Q: How do you ensure the quality of a product from the testing perspective?
A: I follow a mix of risk-based and requirement-based testing. I write detailed test scenarios from the user's
perspective, perform exploratory testing, and continuously communicate with developers/product owners. I
also use metrics like defect density, test coverage, and pass percentage to monitor quality.
Q: How do you test a feature that has no documentation or requirements?
A: I begin with exploratory testing, ask clarifying questions to the product owner, analyze UI behavior, check
API responses, review similar modules, and use logs to understand backend processes.
Q: How do you handle testing when requirements change frequently?
A: I write modular test cases, stay connected with the dev team through agile ceremonies, automate stable
parts of the app, and adapt test plans quickly.
Q: How do you perform risk-based testing?
A: I identify critical business functionalities, prioritize high-impact test cases, and ensure thorough testing for
high-risk areas first.
Automation Testing Questions:
Q: Describe the automation framework you've built or worked with.
A: I developed a modular, data-driven hybrid framework using Selenium WebDriver with TestNG. It includes
Page Object Model, Apache POI, ExtentReports, Maven, and Jenkins integration.
Q: How do you ensure your automation scripts are maintainable and scalable?
A: I follow Page Object Model, use clear naming, centralize configurations, externalize test data, and perform
regular code reviews.
Manual and Automation Testing Interview Q&A - Product Based Companies
Q: What strategies do you use to reduce flaky test cases?
A: I use explicit waits, avoid thread.sleep(), handle dynamic elements robustly, and isolate test cases.
Q: How do you decide what to automate and what not to?
A: Automate repetitive, high-risk flows. Avoid UI that changes frequently or one-time test cases.
Q: Explain how you do version control and CI/CD for your test automation.
A: Scripts are pushed to Git, reviewed via pull requests, and Jenkins handles scheduled/test-triggered
execution with reporting.