Top 20 QA Interview Questions in 2026

1. What is the difference between functional and non-functional testing?

Functional testing verifies that the software does what it's supposed to do — login works, buttons click, forms submit. Non-functional testing checks how well it does it — performance, security, usability, compatibility.

💡 Tip: Always give examples. "Checking login is functional; checking if login loads in under 2 seconds is non-functional."

2. What does a good test case include?

A well-structured test case has: Title, Preconditions, Steps to reproduce, Expected result, Actual result, and Priority/Severity. Some teams also add test data and environment info.

💡 Tip: Mention that good test cases are reusable and independent of each other.

3. Severity vs Priority — what's the difference?

Severity = how bad the bug is technically (critical crash vs cosmetic typo). Priority = how urgently it needs fixing (business decides). A typo in the company CEO's name might be low severity but high priority.

4. When would you use regression testing?

After any code change — bug fixes, new features, refactoring. Regression testing ensures that existing functionality still works after modifications. It's usually automated for efficiency.

5. What is smoke testing?

A quick, shallow test to verify that the most critical functions work after a new build. Think of it as "does the app even turn on?" If smoke testing fails, there's no point in deeper testing.

6. What is the Page Object Model (POM)?

A design pattern where each web page is represented as a class. Elements are stored as properties, actions as methods. This makes tests maintainable — when UI changes, you update one class, not 50 tests.

💡 Tip: This is asked in ~80% of automation interviews. Know it cold.

7. Implicit wait vs Explicit wait in Selenium?

Implicit wait sets a global timeout for finding elements. Explicit wait waits for a specific condition on a specific element (e.g., "wait until this button is clickable"). Explicit is preferred — it's more precise and less flaky.

8. How do you handle dynamic elements?

Use robust locators: data-testid attributes, relative XPath, CSS selectors with partial matches. Combine with explicit waits. Avoid fragile locators like absolute XPath or positional indexes.

9. Selenium vs Playwright vs Cypress — which to choose?

Selenium: mature, multi-language, huge community. Playwright: modern, fast, auto-waiting, multi-browser. Cypress: great DX, but Chrome-focused. For new projects in 2026, Playwright is often the best bet.

10. What is CI/CD and how do tests fit in?

CI (Continuous Integration) = automatically build and test on every commit. CD (Continuous Deployment) = automatically deploy if tests pass. Automated tests run in the CI pipeline — they're the gatekeepers before code reaches production.

11. How do you decide what to automate?

Automate tests that are: repetitive, stable, high-risk, and time-consuming to run manually. Don't automate: one-time tests, rapidly changing UI, or exploratory testing.

12. You found a critical bug right before release. What do you do?

Report immediately with all details. Assess impact with the team. Propose options: hotfix, rollback, or delay release. Document everything. Don't panic — clear communication is key.