Manual Testing

Q1: What is Manual Testing?

Answer:
Manual Testing is the process of testing a software application manually to identify defects, bugs, or issues without using automation tools. Testers execute test cases, verify expected results, and ensure the application meets business and functional requirements.


Q2: What is the difference between Verification and Validation?

Answer:

VerificationValidation
Checks whether the software is built correctlyChecks whether the right software is built
Performed during developmentPerformed after development
Involves reviews, inspections, and walkthroughsInvolves executing the software
Static testingDynamic testing

Q3: Explain the Software Development Life Cycle (SDLC).

Answer:
SDLC is a structured process used to develop software applications.

Phases of SDLC:

  1. Requirement Gathering
  2. Requirement Analysis
  3. System Design
  4. Development (Coding)
  5. Testing
  6. Deployment
  7. Maintenance

Q4: What are the different levels of testing?

Answer:
The four levels of testing are:

  • Unit Testing – Tests individual components.
  • Integration Testing – Tests interactions between modules.
  • System Testing – Tests the complete application.
  • Acceptance Testing (UAT) – Validates the application against business requirements.

Q5: What is the difference between Functional and Non-Functional Testing?

Answer:

Functional TestingNon-Functional Testing
Verifies application functionalityVerifies performance, usability, security, etc.
Based on business requirementsBased on quality attributes
Example: Login functionalityExample: Load testing

Q6: What is the difference between Smoke Testing and Sanity Testing?

Answer:

Smoke TestingSanity Testing
Performed on a new buildPerformed after minor changes or bug fixes
Verifies critical functionalitiesVerifies specific functionality
Wide and shallow testingNarrow and deep testing

Q7: What is the purpose of Test Cases?

Answer:
Test Cases are documents that describe the steps, inputs, expected results, and execution conditions used to verify software functionality.

They help ensure:

  • Requirement validation
  • Repeatable testing
  • Better test coverage
  • Defect identification

Q8: What is a Test Plan and Test Strategy?

Answer:

Test Plan

A Test Plan is a document describing:

  • Scope
  • Objectives
  • Resources
  • Schedule
  • Testing activities
  • Deliverables

Test Strategy

A Test Strategy defines the overall testing approach, including:

  • Testing types
  • Testing levels
  • Test environment
  • Risk management
  • Automation strategy

Q9: What is the difference between Test Scenario and Test Case?

Answer:

Test ScenarioTest Case
High-level testing objectiveDetailed testing steps
Describes what to testDescribes how to test
Covers multiple test casesCovers one scenario

Q10: How do you prioritize Test Cases?

Answer:
Test cases are prioritized based on:

  • Business impact
  • Critical functionality
  • Risk
  • Frequently used features
  • Customer requirements
  • Complexity
  • Previous defects

Q11: What is Test Coverage?

Answer:
Test Coverage measures how much of the application’s functionality has been tested.

Good test coverage ensures:

  • All requirements are validated
  • Critical paths are tested
  • Fewer production defects

Q12: What is Regression Testing?

Answer:
Regression Testing verifies that recent code changes or bug fixes have not affected existing functionality.

It is performed:

  • After bug fixes
  • After enhancements
  • Before production release

Q13: What is Boundary Value Analysis (BVA)?

Answer:
Boundary Value Analysis is a black-box testing technique that focuses on testing boundary values because defects commonly occur at input limits.

Example:

If the valid age is 18–60, test values include:

  • 17
  • 18
  • 19
  • 59
  • 60
  • 61

Q14: What is Equivalence Partitioning?

Answer:
Equivalence Partitioning divides input data into valid and invalid groups (partitions), reducing the number of test cases while maintaining effective coverage.

Example:

Age: 18–60

Valid Partition:

  • 18–60

Invalid Partitions:

  • Below 18
  • Above 60

Q15: What is the Defect Life Cycle?

Answer:
The Defect Life Cycle represents the stages a defect passes through.

Typical stages:

  • New
  • Assigned
  • Open
  • Fixed
  • Retest
  • Verified
  • Closed
  • Reopened (if needed)

Q16: What is the difference between Severity and Priority?

Answer:

SeverityPriority
Impact of the defect on the applicationUrgency to fix the defect
Decided by QADecided by Business/Product Manager
Technical impactBusiness impact

Q17: What is Test Data?

Answer:
Test Data is the input information required to execute test cases.

Examples:

  • Username
  • Password
  • Customer ID
  • Product Code
  • Payment Details

Test Data Preparation involves creating valid, invalid, and boundary data before testing.


Q18: What is Exploratory Testing?

Answer:
Exploratory Testing is an informal testing technique where testers simultaneously learn the application, design test cases, and execute them without predefined scripts.

Advantages:

  • Finds hidden defects
  • Encourages creativity
  • Useful when documentation is limited

Q19: What are the advantages and disadvantages of Manual Testing?

Answer:

Advantages

  • No programming knowledge required
  • Effective for UI and usability testing
  • Better for exploratory testing
  • Cost-effective for small projects

Disadvantages

  • Time-consuming
  • Prone to human errors
  • Difficult for repetitive testing
  • Not suitable for large regression suites

Q20: What is the V-Model in Software Testing?

Answer:
The V-Model (Verification and Validation Model) maps each development phase to a corresponding testing phase.

Development Phase → Testing Phase

  • Requirements → Acceptance Testing
  • System Design → System Testing
  • Architecture Design → Integration Testing
  • Module Design → Unit Testing

It ensures testing starts early in the development lifecycle.


Q21: What is Positive Testing and Negative Testing?

Answer:

Positive Testing

Tests the application using valid inputs to verify expected behavior.

Example: Entering a valid username and password.

Negative Testing

Tests the application using invalid or unexpected inputs to verify error handling.

Example: Entering an invalid password or leaving required fields blank.


Q22: What is Ad-hoc Testing?

Answer:
Ad-hoc Testing is an informal and unplanned testing approach where testers randomly test the application without predefined test cases.

It is useful for:

  • Finding unexpected defects
  • Quick validation
  • Exploratory testing

Q23: How do you ensure good Test Coverage?

Answer:
Good test coverage can be achieved by:

  • Understanding requirements thoroughly
  • Designing comprehensive test scenarios
  • Using Boundary Value Analysis (BVA)
  • Applying Equivalence Partitioning (EP)
  • Performing positive and negative testing
  • Executing regression tests
  • Maintaining a Requirement Traceability Matrix (RTM)

Q24: What is a Test Case Template?

Answer:
A Test Case Template is a standard format used for documenting test cases.

It typically includes:

  • Test Case ID
  • Test Scenario
  • Test Description
  • Preconditions
  • Test Steps
  • Test Data
  • Expected Result
  • Actual Result
  • Status (Pass/Fail)
  • Comments

Q25: What is Test Execution and Test Log?

Answer:

Test Execution

Test Execution is the process of running test cases and comparing the actual results with the expected results.

Test Log

A Test Log records execution details, including:

  • Test Case ID
  • Execution Date
  • Tester Name
  • Status (Pass/Fail)
  • Defects Found
  • Comments

The Test Log helps track testing progress and supports reporting and auditing.