11. What is Functional Testing?
How to answer:
“Functional testing verifies whether the application performs the functions according to the specified requirements.”
Example:
For an e-commerce application:
- 11. What is Functional Testing?
- 12. What is Non-Functional Testing?
- 13. What is Smoke Testing?
- 14. What is Sanity Testing?
- 15. What is Regression Testing?
- 16. What is Retesting?
- 17. What is the difference between Severity and Priority?
- 18. Give an example of High Severity and Low Priority.
- 19. Give an example of Low Severity and High Priority.
- 20. What is a Defect Life Cycle?
- Add product to cart
- Remove product
- Apply coupon
- Place order
- Cancel order
12. What is Non-Functional Testing?
How to answer:
“Non-functional testing evaluates characteristics such as performance, usability, security, compatibility and reliability.”
Example:
“Checking whether the application can handle 5,000 concurrent users would be a performance-related test rather than a basic functional test.”
13. What is Smoke Testing?
How to answer:
“Smoke testing is a high-level check performed on a new build to determine whether the major functionalities are stable enough for detailed testing.”
Example:
For an e-commerce application:
- Application launches
- Login works
- Product search works
- Cart works
- Checkout opens
If these fail, detailed testing may be blocked.
14. What is Sanity Testing?
How to answer:
“Sanity testing is focused testing performed after a minor change or bug fix to verify that the specific functionality and related areas are working correctly.”
Easy difference:
Smoke → Is the build stable enough to test?
Sanity → Does the specific change/fix work correctly?
15. What is Regression Testing?
How to answer:
“Regression testing verifies that existing functionality has not been negatively affected by new changes.”
Example:
If the developer changes the checkout module, I would test:
- Checkout
- Payment
- Order creation
- Order confirmation
- Related cart functionality
16. What is Retesting?
How to answer:
“Retesting means executing the failed test again after the defect has been fixed to verify that the specific defect is resolved.”
Remember:
Retesting → Verify the fix
Regression → Verify existing functionality hasn’t broken
17. What is the difference between Severity and Priority?
How to answer:
Severity = Technical/business impact of the defect
Priority = How quickly the defect should be fixed
Example:
A spelling mistake on the homepage could have:
Low Severity + High Priority
if the page is part of a major marketing campaign.
18. Give an example of High Severity and Low Priority.
Answer:
“Suppose an admin-only report crashes when a rarely used option is selected. The crash could technically be high severity, but because the feature is rarely used and there is a workaround, the priority could be low.”
19. Give an example of Low Severity and High Priority.
Answer:
“Suppose the company name is displayed incorrectly on the main homepage just before a major client demonstration. Technically it may be a low-severity UI issue, but business urgency could make its priority high.”
20. What is a Defect Life Cycle?
How to answer:
Explain the journey:
New → Assigned → Open → Fixed → Retest → Verified → Closed
Depending on the organization, additional statuses may include:
- Reopened
- Rejected
- Duplicate
- Deferred
- Cannot Reproduce
Interview Tip:
Say:
“The exact workflow can vary depending on the organization’s defect management process.”