Manual Testing Interview Questions and Answers (Part-I)

Q21. What is Test Harness?

Answer:
A Test Harness is a set of tools and test data configured to test an application under different conditions. It helps compare actual output with the expected output to verify correctness.

Benefits:

• Automates the testing process, increasing productivity.
  
• Ensures better quality in the software being tested.
  

---

Q22. What is the Difference Between Bug Log and Defect Tracking?

Answer:

• Bug Log:
  A document that shows the status of defects (open, closed, reopened, or deferred) in a particular module.
  
• Defect Tracking:
  A process used to track the defect’s symptoms, reproducibility, severity, priority, and current status.
  

---

Q23. What are Integration Testing and Regression Testing?

Answer:

• Integration Testing:
  
  • Combines software modules and tests their interaction.
    
  • Ensures proper data flow and communication.
    
  • Performed by both developers and testers.
    
  • Uses white-box and black-box techniques.
    
• Regression Testing:
  
  • Re-tests the application after bug fixes.
    
  • Ensures that existing functionality is not broken.
    
  • Performed by testers.
    

---

Q24. What is Peer Review in Software Testing?

Answer: Peer Review is an informal or formal process where colleagues examine each other’s work products to find defects and suggest improvements.

Types:

• Inspection: Formal, detailed review (e.g., Motorola’s Iridium project).
  
• Team Review: Structured but less formal.
  
• Walkthrough: Informal discussion about the work product.
  
• Pair Programming: Two developers write and review code together.
  
• Peer Desk Check: One person reviews with defect checklists.
  
• Passaround: Multiple people review and comment concurrently.
  

---

Q25. What is Compatibility Testing? Give an Example.

Answer: Compatibility Testing ensures that an application works correctly across different environments like:

• Operating Systems
  
• Browsers
  
• Databases
  
• Hardware platforms
  
• Peripheral devices
  

Example:
Testing a game app on various computers to check if it works correctly on different configurations (RAM, processor, OS).

---

Q26. What is a Traceability Matrix?

Answer: A Traceability Matrix is a document that maps:

• Requirements to
  
• Test Cases and
  
• Defects
  

It ensures complete test coverage and helps trace back defects to the original requirement.

---

Q27. Explain Boundary Value Testing and Equivalence Testing with Examples.

Answer:

• Boundary Value Testing (BVA):
  Focuses on testing values at the edge of input boundaries.
  Example: For a field that accepts 4–10 characters:
  
  • Test with: 3 (fail), 4 (pass), 5 (pass), 9 (pass), 10 (pass), 11 (fail)
    
• Equivalence Partitioning:
  Divides input into valid/invalid groups.
  Example: If input should be lowercase letters:
  
  • Valid: a–z
    
  • Invalid: A–Z, 0–9, special chars
    

---

Q28. What is Security Testing?

Answer: Security Testing ensures that confidential data remains protected from unauthorized access (internal or external). It involves:

• Functional Security Testing
  
• Penetration Testing
  
• Access Verification
  

Goal: To identify vulnerabilities in the system.

---

Q29. What is Installation Testing?

Answer: Installation Testing checks if software and hardware components are installed and configured correctly. It also:

• Verifies high-volume data handling
  
• Checks for correct error messaging
  
• Confirms that security settings are in place
  

---

Q30. What is AUT?

Answer: AUT stands for Application Under Test.
It refers to the software application being tested after the development phase and before production.

Q31. What is Defect Leakage?

Answer:
Defect leakage means a bug or issue that is found by the customer after the software has been delivered or released. It shows that some bugs were not caught during testing and were leaked into the final product.
Also called: Bug Leakage

---

Q32. What should be included in a good Bug Report?

Answer:
A good bug report helps developers understand and fix the issue quickly. It should include:

1. Project Name
   
2. Bug Title (Subject)
   
3. Description (what is the issue?)
   
4. Summary
   
5. Detected By (Tester’s Name)
   
6. Assigned To (Developer’s Name)
   
7. Version in which bug was found
   
8. Version in which bug was fixed
   
9. Date Detected
   
10. Expected and Actual Closure Dates
    
11. Priority (High/Medium/Low/Urgent)
    
12. Severity (1 to 5 scale)
    
13. Current Status (Open, Fixed, etc.)
    
14. Bug ID
    
15. Screenshot or Attachment (if needed)
    
16. Failed Test Case (if any)
    

---

Q33. What is Error Guessing and Error Seeding?

Answer:

• Error Guessing: A tester uses experience and intuition to guess areas where bugs might occur and writes test cases for them.
  
• Error Seeding: Known errors are intentionally added to the software to check how many bugs the test process is able to find. It helps in measuring test effectiveness.
  

---

Q34. What is Ad-hoc Testing?

Answer:
Ad-hoc testing means testing without any formal plan or documentation. It is done randomly and is mostly based on the tester’s understanding of the application. It helps find bugs that regular test cases might miss.

---

Q35. What are some basic solutions to common software development problems?

Answer:
Here are some solutions:

1. Clear Requirements: Well-documented, detailed, testable requirements.
   
2. Realistic Schedules: Enough time for development, testing, bug fixing.
   
3. Early Testing: Begin testing early and do re-testing properly.
   
4. Change Management: Handle requirement changes smoothly.
   
5. Good Communication: Regular meetings, updates, and coordination with team members and customers.
   

---

Q36. What are the common problems in the software development process?

Answer:

1. Unclear Requirements: Client gives incomplete or confusing requirements.
   
2. Tight Deadlines: Developers get less time to complete work.
   
3. Less Testing: Not enough time spent on testing.
   
4. Multitasking: Testers or developers are asked to handle multiple projects.
   
5. Poor Communication: Misunderstanding between developers and clients.
   

---

Q37. What is the difference between Software Testing and Quality Assurance (QA)?

Answer:

• Software Testing is about finding bugs in the application (focused on detection).
  
• Quality Assurance (QA) is about improving the whole process of software development and preventing bugs (focused on prevention).
  

---

Q38. How would you test a water bottle?

Answer:
Some test ideas:

• Check size and shape of the bottle (looks like a bottle?)
  
• Test if the cap fits tightly
  
• See if it leaks when tilted
  
• Check if it’s usable for cold and hot water
  
• Drop test to see if it breaks
  
• Test material quality (plastic/glass)
  
• Check if it’s recyclable
  
• Try with different liquids
  
• Check comfort when drinking directly
  This kind of testing is known as Usability and Stress Testing.
  

---

Q39. What is Portlet Testing?

Answer:
Portlet testing is done on small application blocks inside a web portal. Main areas to test:

• Proper size and alignment in portal layout
  
• Buttons and links work correctly
  
• Preference settings are saved/loaded properly
  
• Backend communication is working
  
• Supported languages work fine
  
• Passwords/secure info is not visible in plain text
  
• Check backward compatibility with old versions
  

---

Q40. What is Equivalence Partitioning?

Answer:
It is a test design technique where input data is divided into equal classes or groups. If one value in a group works, other values in that group are expected to work too.
It helps reduce the number of test cases while ensuring good coverage.