Manual Testing Interview Questions and Answers (Level-1)

Q1. What is the difference between Functional and Non-Functional Requirements?

Answer: In software testing, understanding the difference between functional and non-functional requirements is fundamental.

• Functional Requirements describe what the system should do. These requirements define system behavior, features, and functionalities. Examples include:
  
  • Login authentication
    
  • Business logic and calculations
    
  • Data processing and storage
    
  • User input validation
    
  • Report generation
    
• Non-Functional Requirements define how the system should behave under certain conditions. These are quality attributes like:
  
  • Performance (response time under load)
    
  • Scalability
    
  • Security
    
  • Usability
    
  • Reliability
    
  • Maintainability
    

---

Q2. How are Severity and Priority related in Software Testing?

Answer:

• Severity refers to the impact of a bug on the functionality of the software.
  
• Priority refers to the urgency with which a bug should be fixed.
  

Factor	Severity	Priority
Perspective	Application’s functional impact	Business or customer requirement
Set By	Tester	Project Manager/Client

Example:

• A crash on the login page = High Severity & High Priority
  
• A typo in the footer = Low Severity & High Priority
  

---

Q3. What are the different types of Severity Levels in Testing?

Answer: Here are common severity classifications for defects:

1. Low Severity: Cosmetic issues like font color, UI alignment
   
2. Medium Severity: Issues like form validation or boundary-related bugs
   
3. High Severity: Major functionality failures like:
   
   • Calculation errors
     
   • System crashes
     
   • Data corruption
     
   • Inter-system communication failures
     

---

Q4. What is the difference between Priority and Severity with Examples?

Answer:

Category	Priority	Severity
Definition	Fix order based on business needs	Impact on software functionality
Who sets it?	Project Manager / Client	Tester
Example	Wrong logo on homepage – High Priority, Low Severity	App crash on clicking a rarely used link – Low Priority, High Severity

🔥 Examples:

• High Severity, Low Priority: App crashes on an obscure feature
  
• Low Severity, High Priority: Spelling error on company name
  
• High Severity, High Priority: Payment system fails
  
• Low Severity, Low Priority: Alignment issue on About Us page
  

---

Q5. What is Bucket Testing (A/B Testing)?

Answer: Bucket Testing or A/B Testing is used to compare two versions of a webpage or feature to determine which one performs better.

How it works:

• Users are split into groups (Group A and Group B).
  
• Group A sees the original version, and Group B sees a new version.
  
• User engagement metrics like clicks, conversions, and time on page are analyzed.
  

---

Q6. What is Entry and Exit Criteria in Software Testing?

Answer:

Entry Criteria define when to start testing.
Exit Criteria define when to stop testing.

Entry Criteria:

• Approved SRS, FRS
  
• Ready Test Cases
  
• Environment Setup
  
• Code deployment complete
  

Exit Criteria:

• All test cases executed
  
• No critical defects remaining
  
• Test Summary Report created
  
• Sign-off from stakeholders
  

---

Q7. What is Concurrency Testing?

Answer: Concurrency Testing checks how a system behaves when multiple users access it at the same time.

Tools used: LoadRunner, JMeter
Goals:

• Identify deadlocks
  
• Measure response time
  
• Analyze performance under multi-user load
  

Example: 100 users logging in simultaneously during a flash sale.

---

Q8. What is Statement/Code/Line Coverage in White Box Testing?

Answer: Statement Coverage ensures each line of code is tested at least once.

Benefits:

• Finds unused code
  
• Ensures logic completeness
  
• Improves code quality
  
• Formula:
• Statement Coverage = (Number of Executed Statements / Total Statements) × 100%

---

Q9. What is Branch Coverage/Decision Coverage?

Answer: Branch Coverage ensures every possible decision (true/false conditions) is tested.

Formula:
Branch Coverage = (Executed Branches / Total Branches) × 100%

Helps ensure all decision paths (like if, else, switch) are tested to prevent hidden bugs.

---

Q10. What is the difference between High-Level and Low-Level Test Cases?

Answer:

Type	High-Level Test Cases	Low-Level Test Cases
Focus	Major functions or features	UI and field-level validation
Example	“Verify user can login successfully”	“Verify password textbox hides characters”

---

Q11. What is Localization Testing with Example?

Answer: Localization Testing ensures that an app adapts properly to a specific language, region, or culture.

Examples:

• Text translated accurately (e.g., English to Arabic)
  
• Calendar format adjusted (Gregorian vs Hijri)
  
• Legal/Religious features (e.g., Islamic Banking rules: No interest, halal businesses only)
  

---

Q12. What is Risk Analysis in Software Testing?

Answer: Risk Analysis involves identifying, analyzing, and mitigating potential risks during testing.

Common Risks:

• Requirement changes
  
• Time crunch
  
• Resource unavailability
  
• Missed critical defects
  

Solutions:

• Prioritize high-risk features
  
• Allocate skilled testers accordingly
  
• Regular review meetings
  

---

Q13. Difference between Two-Tier and Three-Tier Architecture?

Answer:

Type	Two-Tier Architecture	Three-Tier Architecture
Layers	Client and Server	Client, Server (Business Logic), Database
Example	Desktop application with direct DB access	Web application with backend server logic

---

Q14. Difference between Static and Dynamic Testing?

Answer:

Static Testing (Verification)	Dynamic Testing (Validation)
Performed without execution	Performed by running the application
Code reviews, walkthroughs	Unit, System, Acceptance Testing
Low cost, early bug detection	Real-time behavior validation

Q15. Explain Use Case Diagram. What are the attributes of use cases?

Answer:

A Use Case Diagram is a graphical representation that gives an overview of the functionality of a system. It is used during the analysis phase of software development to specify the system’s behavior from the user’s perspective.

Key Components of Use Case Diagram:

1. Actors: These are external entities such as users, hardware, or software that interact with the system.
   
2. Use Cases: The functionalities or behaviors that the system performs in response to actor actions.
   
3. Associations: Lines connecting actors to use cases to show the interactions between them.
   

Attributes of Use Cases:

• Actor: External user/system interacting with the system.
  
• Preconditions: The conditions that must be met before the use case begins.
  
• Basic Flow: The main sequence of steps that define the use case’s typical behavior.
  
• Alternate Flow: Variations from the basic flow.
  
• Postconditions: The conditions after the use case has executed successfully.
  

---

Q16. What is Web Application Testing? Explain the different phases in Web Application Testing?

Answer:

Web Application Testing involves testing a website to ensure its performance, security, usability, compatibility, and overall functionality.

Phases of Web Application Testing:

1. Web Tier Testing:
   
   • Tests the browser compatibility of the application (e.g., Chrome, Firefox, IE).
     
2. Middle Tier Testing:
   
   • Verifies the functionality and security of the application’s middle layer (e.g., business logic layer).
     
3. Database Tier Testing:
   
   • Checks the database integrity and the correctness of data in the database.
     

---

Q17. Explain Unit Testing, Interface Testing, and Integration Testing. Also explain the types of Integration Testing briefly?

Answer:

Unit Testing:

• Unit Testing is performed to check the functionality of individual modules of a system. It is typically done by developers in their local development environment.
  

Interface Testing:

• Interface Testing ensures that modules of a system communicate properly as per specifications. It often focuses on user interface (UI) elements.
  

Integration Testing:

• Integration Testing checks whether multiple individual modules, once combined, function as expected.
  

Types of Integration Testing:

1. Big Bang Integration Testing:
   
   • All modules are integrated at once, and tested together.
     
   • Drawback: Difficult to identify the source of defects.
     
2. Top-Down Integration Testing:
   
   • Starts by testing the main module, followed by the sub-modules.
     
   • Uses Stubs for unready modules.
     
3. Bottom-Up Integration Testing:
   
   • Begins testing from sub-modules and moves to the main module.
     
   • Uses Drivers as temporary replacements for higher-level modules.
     

---

Q18. Explain Alpha, Beta, and Gamma Testing?

Answer:

Alpha Testing:

• Conducted in-house by developers or testers to check the functionality before it is released to external users. The alpha release is the first version tested.
  

Beta Testing:

• Beta Testing is conducted by end users in a controlled environment. Feedback is collected to fix any bugs before the beta release.
  

Gamma Testing:

• Done when the software is almost ready for release, skipping in-house testing and directly going to the end-users.
  

---

Q19. Explain the methods and techniques used for Security Testing?

Answer:

Security Testing ensures that software is secure from vulnerabilities. Here are some common methods:

1. Black Box Testing: Testing without knowledge of internal code.
   
2. White Box Testing: Involves testing with full knowledge of the system’s internal code.
   
3. Database Testing: Validates the integrity of data in the database.
   
4. Session Hijacking: Attacking active user sessions through techniques like IP Spoofing.
   
5. Email Spoofing: Fake emails are sent to appear as if they come from trusted sources.
   
6. Content Spoofing: Creating fake websites to steal user credentials.
   
7. Phishing: Sending fraudulent emails to obtain sensitive information.
   

Penetration Testing and SQL Injection are also used to identify potential vulnerabilities in web applications and databases.

---

Q20. Explain IEEE 829 standards and other Software Testing standards?

Answer:

IEEE 829 is a software testing standard that defines the format and content for various test documents used during the testing phase. These include:

1. Test Plan: Documents the scope, resources, and duration for testing.
   
2. Test Design: Contains test pass criteria, test conditions, and expected results.
   
3. Test Case: Describes specific test data and conditions.
   
4. Test Procedure: Lists the steps to execute the test.
   
5. Test Log: Records the status of tests executed.
   
6. Test Incident Report: Describes failed test cases and expected vs actual results.
   
7. Test Summary Report: Summarizes testing results, quality, and requirements compliance.
   

Other related standards:

• IEEE 1008: For Unit Testing.
  
• IEEE 1012: For Software Verification and Validation.
  

IEEE 1061: For Software Metrics.

The Next 20 Questions-I: MANAUL TESTING