← back
✅ Manual Testing Interview Q&A
🧠 With Detailed Explanations + Real Examples
🔹 1. What is Software Testing?
Software testing is the process of evaluating a software application to ensure it meets the business requirements and works as expected. It helps identify bugs or defects early in the development cycle.
✅ Example: Testing a shopping cart to check if items are added correctly before the app is released to users.
🔹 2. What is Manual Testing?
Manual testing is the type of testing where testers manually run the test cases without using automation tools like Selenium. It focuses on how the application behaves for real users.
✅ Example: Manually testing the login page by entering different usernames and passwords.
🔹 3. Why is Testing Important?
Testing helps improve software quality by finding bugs early and reducing the risk of failure after release. It ensures the software is reliable, secure, and works correctly for users.
✅ Real World: A bug in banking software could result in financial loss, so testing is crucial.
🔹 4. What is a Defect or Bug?
A defect or bug is a flaw or error in the software that causes it to produce incorrect or unexpected results. It usually happens due to coding mistakes, design errors, or wrong requirements.
✅ Example: If clicking "Submit" does nothing on a form, it's a bug.
🔹 5. What is the Difference Between Error, Defect, and Failure?
-
Error – Mistake by a developer (e.g., wrong formula in code)
-
Defect – A flaw found in testing (e.g., wrong total displayed)
-
Failure – When the system doesn't work in real use (e.g., app crashes when a user clicks a button)✅ Tip: Error → Defect → Failure (like a chain reaction)
🔹 6. What is a Test Case?
A test case is a detailed step-by-step document that explains how to test a feature. It includes input data, steps to perform, and the expected result.
✅ Example:
-
Input: Enter correct username and password
-
Action: Click login
-
Expected: User should be logged in successfully
🔹 7. What is a Test Scenario?
A test scenario describes what needs to be tested in simple terms. It's a high-level idea or situation for testing.
✅ Example: "Verify the login functionality for valid and invalid credentials."
🔹 8. What is a Test Plan?
A test plan is a document that outlines the scope, objectives, tools, timelines, and responsibilities of the testing process. It helps manage the overall testing effort.
✅ Key Elements: Test items, features to be tested, test schedule, deliverables, and exit criteria.
🔹 9. What is Test Data?
Test data is the input values used during testing to check how the software behaves. It includes both valid and invalid data to test different conditions.
✅ Example: Valid – Email: user@test.com, Invalid – Email: user@.com
🔹 10. What is a Test Environment?
A test environment is the setup where testing is done. It includes hardware, software, network, databases, and tools that support test execution.
✅ Example: Using a staging server that’s a copy of the production server.
🔹 11. What is Quality Assurance (QA)?
QA is a process-focused activity that ensures the right methods and processes are used during software development to prevent defects.
✅ Example: Implementing a checklist for coding standards or reviewing requirements.
🔹 12. What is Quality Control (QC)?
QC is product-focused and involves finding defects in the final product using various testing techniques. It ensures the output is bug-free.
✅ Difference: QA prevents bugs, QC finds them.
🔹 13. What is SDLC (Software Development Life Cycle)?
SDLC is a process used to build software in a structured way. It includes stages like planning, designing, coding, testing, deployment, and maintenance.
✅ Models: Waterfall, Agile, V-Model, Spiral
✅ Example: In Agile SDLC, features are developed and tested in short cycles (sprints).
🔹 14. What is STLC (Software Testing Life Cycle)?
STLC is a set of activities performed during the testing process, like requirement analysis, test planning, test case design, execution, defect reporting, and closure.
✅ Important: Testing is not just execution — planning and closure are also key.
🔹 15. What is Black Box Testing?
In black box testing, we test the software without looking at the internal code or logic. It focuses only on inputs and outputs.
✅ Example: Test a calculator by entering numbers, not by looking at its code.
🔹 16. What is White Box Testing?
White box testing involves testing the internal code, logic, and structure of the software. It’s mostly done by developers.
✅ Example: Unit testing a loop to check all possible conditions.
🔹 17. What is Grey Box Testing?
Grey box testing is a mix of black box and white box testing. The tester knows some internal details of the system but still tests it from the outside.
✅ Use Case: Useful for integration testing where knowledge of the backend helps.
🔹 18. What is Static Testing?
Static testing means checking the code, documents, or requirements without executing the program. It is done through reviews, walkthroughs, and inspections.
✅ Benefit: It catches issues early, saving time and cost.
🔹 19. What is Dynamic Testing?
Dynamic testing means running the application and checking its behavior with real input. It helps verify that the software functions correctly during runtime.
✅ Example: Clicking buttons, entering data, and checking outputs.
🔹 20. What is Validation in Testing?
Validation checks whether the software actually fulfills the user’s needs and business goals. It’s done after the product is built.
✅ Question: Did we build what the user wants?
🔹 21. What is Verification in Testing?
Verification ensures that the product is built according to specifications and design. It is done throughout the development process.
✅ Question: Did we build the product correctly?
🔹 22. What is Usability Testing?
Usability testing checks how easy and convenient the software is for users. It looks at layout, readability, navigation, and user satisfaction.
✅ Example: Is the sign-up form easy to fill on both mobile and desktop?
🔹 23. What is Functional Testing?
Functional testing checks whether each feature or function of the application works as expected based on requirements.
✅ Includes: Smoke, sanity, regression, integration, and system testing.
🔹 24. What is Non-Functional Testing?
Non-functional testing evaluates system performance, like how fast it works, how secure it is, and how it handles many users.
✅ Example: Testing how the site performs with 1,000 users logging in at once.
🔹 25. What is Regression Testing?
Regression testing is done after changes or bug fixes to make sure nothing else is broken. It re-runs previously passed test cases.
✅ Real Case: After fixing the login bug, you also test the dashboard, logout, and settings to be safe.
🔹 26. What is Sanity Testing?
Sanity testing is a quick check to ensure that major functionalities are working fine after a build or bug fix. It is done before deeper testing to save time.
✅ Example: After fixing a login bug, check if login works — don’t test every button.
🔹 27. What is Smoke Testing?
Smoke testing is a high-level test to confirm if the basic features of a software build are stable enough for further testing. It’s also known as "build verification testing".
✅ Tip: Think of it as a basic health check before doing full body tests.
🔹 28. What is Exploratory Testing?
Exploratory testing is done without pre-written test cases. Testers explore the app freely and learn as they test. It relies on the tester’s intuition and experience.
✅ Use Case: Great for new apps or when requirements are unclear.
🔹 29. What is Ad Hoc Testing?
Ad hoc testing is an informal testing method where testers try to break the system randomly without any structured plan.
✅ Note: No documentation is used; just tester creativity.
🔹 30. What is Retesting?
Retesting is testing a specific bug or feature again after it was fixed to ensure the issue has been resolved.
✅ Tip: It is always done with the same data that previously failed.
🔹 31. What is Compatibility Testing?
Compatibility testing checks if the software works well on different devices, browsers, OS versions, and network conditions.
✅ Example: Testing an app on Android, iOS, Windows, and Mac.
🔹 32. What is Cross Browser Testing?
This testing checks whether a website works correctly across different browsers like Chrome, Firefox, Safari, and Edge.
✅ Reason: Each browser renders web pages differently.
🔹 33. What is Localization Testing?
Localization testing checks whether the software is correctly translated and adapted for a specific region or language.
✅ Example: Checking if prices are shown in rupees (₹) in Indian version.
🔹 34. What is Globalization Testing?
Globalization testing ensures the software can be used across multiple languages and regions without code change. It’s not language-specific like localization.
✅ Tip: Think of it as testing the ability to support any region.
🔹 35. What is Accessibility Testing?
Accessibility testing checks if the application is usable by people with disabilities (like vision or hearing problems). It ensures compliance with standards like WCAG.
✅ Tools: NVDA, JAWS, WAVE
🔹 36. What is End-to-End Testing?
End-to-end testing checks the complete workflow of an application from start to finish. It ensures all integrated parts work together as expected.
✅ Example: From login to placing an order to payment confirmation.
🔹 37. What is Boundary Value Analysis (BVA)?
BVA is a test design technique that focuses on testing the boundary values of input fields (like minimum, maximum, just below and above).
✅ Example: If a field accepts 1–100, test 0, 1, 100, 101.
🔹 38. What is Equivalence Partitioning?
This technique divides input data into valid and invalid groups. You test only one value from each group, assuming others will behave the same.
✅ Benefit: Saves time by reducing the number of test cases.
🔹 39. What is Decision Table Testing?
It is used for testing combinations of inputs using a table format. It's especially useful for business logic like loan approvals or discount rules.
✅ Example: If A and B conditions are met, then action C happens.
🔹 40. What is State Transition Testing?
This technique checks how software behaves in different states and how it transitions between them.
✅ Example: Logging in → Dashboard → Logout → Login again.
🔹 41. What is Use Case Testing?
Use case testing is based on use cases that describe how a user interacts with the system. It tests complete user flows.
✅ Example: Booking a hotel room from start to confirmation.
🔹 42. What is Defect Life Cycle?
It is the journey of a bug from when it’s found to when it's closed. Stages include New → Assigned → Open → Fixed → Retested → Closed.
✅ Tip: Helps track bug status.
🔹 43. What is Severity in Testing?
Severity is how serious the defect is in terms of impact on the system. High severity bugs break core features.
✅ Example: App crash is high severity.
🔹 44. What is Priority in Testing?
Priority defines how soon the defect should be fixed. A high priority issue is one that must be resolved urgently, even if it’s not severe.
✅ Example: Wrong company logo is low severity but high priority.
🔹 45. Difference Between Severity and Priority?
-
Severity: Impact on the software
-
Priority: Urgency of fixing the bug✅ Trick: Severity = technical, Priority = business
🔹 46. What is a Bug Report?
A bug report is a document that describes the problem found, steps to reproduce, screenshots (if needed), and expected vs actual results.
✅ Purpose: Helps developers understand and fix the issue quickly.
🔹 47. What is Test Summary Report?
A test summary report is a final report that explains overall testing details — total test cases, passed, failed, defects found, and testing coverage.
✅ Shared at end of test cycle.
🔹 48. What is Agile Testing?
Agile testing follows agile methodology where testing is done in small, quick cycles (sprints). It involves continuous testing and regular feedback.
✅ Note: Testers work closely with developers.
🔹 49. What is Sprint in Agile?
A sprint is a fixed time period (usually 2–4 weeks) where a small part of the software is developed and tested.
✅ Goal: Deliver working software after every sprint.
🔹 50. What is Scrum in Agile?
Scrum is a popular agile framework that divides work into sprints and includes roles like Scrum Master, Product Owner, and team. It focuses on team collaboration.
✅ Meetings: Daily stand-ups, sprint planning, reviews.
🔹 51. What is System Testing?
System testing is the process of testing the complete application as a whole. It checks if the system meets the specified requirements and works correctly in all scenarios.
✅ Example: Testing a food delivery app from login to placing an order to tracking.
🔹 52. What is Integration Testing?
Integration testing verifies the interaction between different modules or components of an application. It ensures that combined parts work well together.
✅ Example: Testing if the login module correctly links with the dashboard.
🔹 53. What is Unit Testing?
Unit testing involves testing individual pieces of code (functions or methods) in isolation. It’s usually done by developers.
✅ Tools: JUnit, NUnit, TestNG
🔹 54. What is Acceptance Testing?
Acceptance testing checks whether the final product meets the business requirements and is ready for delivery to the customer. It is the last level of testing.
✅ Types: Alpha testing, Beta testing
🔹 55. What is Alpha Testing?
Alpha testing is done by internal testers or the development team before releasing the product to external users. It helps catch major bugs early.
✅ Location: Done at the developer’s site.
🔹 56. What is Beta Testing?
Beta testing is done by real users in a real environment before the final release. It helps get feedback from actual customers.
✅ Tip: It's like a soft launch of the software.
🔹 57. What is Performance Testing?
Performance testing checks how fast the system responds under different loads. It helps find bottlenecks in speed, scalability, and stability.
✅ Types: Load testing, Stress testing
🔹 58. What is Load Testing?
Load testing determines how the system behaves under expected user loads. It measures response time, throughput, and resource usage.
✅ Example: Testing if a site handles 1000 users at the same time.
🔹 59. What is Stress Testing?
Stress testing pushes the system beyond normal conditions to see how it behaves under extreme stress. It identifies the breaking point.
✅ Example: Testing a payment app during peak festival sales.
🔹 60. What is Volume Testing?
Volume testing checks the system performance when handling a large amount of data. It ensures the app can process high data loads smoothly.
✅ Example: Uploading a file with 10 million records.
🔹 61. What is Scalability Testing?
Scalability testing checks whether the application can handle increasing user loads and data without affecting performance.
✅ Tip: It ensures the system can grow with demand.
🔹 62. What is Security Testing?
Security testing identifies vulnerabilities and ensures the system protects data from unauthorized access and threats.
✅ Checks: Login protection, encryption, session handling
🔹 63. What is Penetration Testing?
Penetration testing is an ethical hacking process to find security weaknesses that attackers could exploit.
✅ Tools: Metasploit, Burp Suite
🔹 64. What is Risk-Based Testing?
Risk-based testing prioritizes test cases based on the risk of failure. Higher risk features are tested first.
✅ Tip: Saves time and focuses on critical areas.
🔹 65. What is Test Coverage?
Test coverage is a metric that shows how much of the application has been tested. Higher coverage means fewer untested parts.
✅ Types: Requirement coverage, code coverage
🔹 66. What is Code Coverage?
Code coverage measures how much of the source code is tested by automated tests. It helps identify untested code paths.
✅ Tools: JaCoCo, Cobertura
🔹 67. What is Defect Density?
Defect density = Total defects / Size of the software module. It shows the number of defects in a given size of code.
✅ Use: To measure code quality over time.
🔹 68. What is the Difference Between QA and Testing?
-
QA: Process-oriented, aims to prevent defects
-
Testing: Product-oriented, aims to find defects✅ QA = Prevention, Testing = Detection
🔹 69. What is Negative Testing?
Negative testing ensures the software handles invalid input or actions gracefully without crashing.
✅ Example: Entering letters into a phone number field.
🔹 70. What is Positive Testing?
Positive testing checks if the application behaves correctly with valid data or input. It confirms the expected functionality works.
✅ Example: Entering a valid username and password.
🔹 71. What is a Test Suite?
A test suite is a collection of test cases that are grouped together for execution. It may be for a specific module or feature.
✅ Example: A test suite for the login module.
🔹 72. What is a Test Strategy?
A test strategy is a high-level document that defines the testing approach, objectives, resources, and timelines for the entire project.
✅ Created by: Test Manager or QA Lead
🔹 73. What is Test Closure?
Test closure refers to all the activities done at the end of testing like analyzing test results, documenting defects, and submitting a final report.
✅ Outcome: Test Summary Report
🔹 74. What is a Traceability Matrix?
A traceability matrix is a document that maps requirements to test cases to ensure all functionalities are tested.
✅ Helps: Identify missing test coverage.
🔹 75. What is the Role of a Manual Tester in Agile?
A manual tester in agile participates in sprint planning, creates and executes test cases during sprints, logs defects, and collaborates closely with developers.
✅ Important: Continuous testing and feedback.
🔹 76. What is Sanity Testing?
Sanity testing is done to check whether a specific bug fix or functionality is working properly. It’s a narrow, focused form of regression testing.
✅ Example: After fixing login issue, tester checks only login module.
🔹 77. What is Regression Testing?
Regression testing ensures that recent code changes haven't broken the existing functionalities. It verifies the overall system stability.
✅ Tip: Performed after every code change or release.
🔹 78. What is Retesting?
Retesting is the process of testing the same test case again after fixing a defect to ensure the bug is actually resolved.
✅ Focus: Only the failed test cases are executed again.
🔹 79. What is a Test Environment?
A test environment includes hardware, software, and network configuration where testers run tests. It should resemble the production environment as closely as possible.
✅ Includes: Server, OS, database, browsers, etc.
🔹 80. What is a Test Lab?
A test lab is a controlled and isolated environment where testers perform various types of testing. It includes all necessary tools and systems required.
✅ Goal: Simulate production without impacting real users.
🔹 81. What is Compatibility Testing?
Compatibility testing checks whether the application works properly across different browsers, OS, devices, and network environments.
✅ Example: Testing a website in Chrome, Firefox, Safari, etc.
🔹 82. What is Usability Testing?
Usability testing evaluates the software’s user interface and user experience. It checks if the app is easy to use and intuitive.
✅ Involves: Real users performing real tasks.
🔹 83. What is GUI Testing?
GUI testing focuses on checking graphical elements like buttons, icons, menus, and layouts. It ensures they work and look as expected.
✅ Checks: Font size, alignment, colors, behavior.
🔹 84. What is Compliance Testing?
Compliance testing ensures that the application meets industry standards, regulations, or laws. It’s important in healthcare, finance, etc.
✅ Example: GDPR, HIPAA compliance.
🔹 85. What is Internationalization Testing?
Internationalization testing checks whether the application can be adapted to different languages and regions without code changes.
✅ Goal: Ensure support for global use.
🔹 86. What is Localization Testing?
Localization testing checks if the application works correctly in a specific region or language. It includes date format, currency, translation, etc.
✅ Example: Showing ₹ in India and $ in the US.
🔹 87. What is Recovery Testing?
Recovery testing checks how well the system recovers after a crash, failure, or unexpected shutdown.
✅ Goal: Ensure data safety and system stability after failure.
🔹 88. What is Installation Testing?
Installation testing ensures the software installs and uninstalls properly in different environments without issues.
✅ Includes: Setup, configuration, uninstallation.
🔹 89. What is Mutation Testing?
Mutation testing involves modifying the program’s code slightly to check if the test cases catch the changes. It helps measure test effectiveness.
✅ If tests fail: Tests are good.
🔹 90. What is A/B Testing?
A/B testing compares two versions of an application to determine which performs better. Common in marketing and UI optimization.
✅ Used in: Web design, product experiments.
🔹 91. What is Static Testing?
Static testing involves reviewing documents, code, or requirements without executing the program.
✅ Example: Reviewing code, walkthroughs, peer reviews.
🔹 92. What is Dynamic Testing?
Dynamic testing involves executing the code and checking the application behavior.
✅ Includes: Unit, system, integration testing.
🔹 93. What is Monkey Testing?
Monkey testing is random testing done without test cases to try and break the system.
✅ Example: Random clicks, inputs by a tester.
🔹 94. What is Exploratory Testing?
Exploratory testing is where testers learn the application and design tests on the fly. It's based on tester creativity and experience.
✅ Useful when: No time for scripted testing.
🔹 95. What is Session-Based Testing?
Session-based testing is a structured way of exploratory testing, performed in time-boxed sessions with clear goals.
✅ Report: Includes session notes and test coverage.
🔹 96. What is Ad Hoc Testing?
Ad hoc testing is unplanned testing done without any documentation or plan to break the system randomly.
✅ Goal: Discover defects missed in formal testing.
🔹 97. What is Grey Box Testing?
Grey box testing is a mix of white box and black box testing. The tester has partial knowledge of the internal workings.
✅ Example: API testing with known request/response format.
🔹 98. What is Manual Testing Lifecycle?
It includes requirement analysis → test planning → test case design → environment setup → test execution → defect logging → test closure.
✅ A structured flow for manual QA.
🔹 99. What is a Bug Life Cycle?
The bug life cycle describes the stages a defect goes through from discovery to closure: New → Assigned → Open → Fixed → Retested → Closed/Rejected.
✅ Tracks progress and ownership.
🔹 100. What is a Severity vs Priority in Defect?
-
Severity: Impact of the bug on the application
-
Priority: Urgency of fixing the bug✅ Example: Login failure = High severity & priority
🔹 76. What is Sanity Testing?
Sanity testing is done to check whether a specific bug fix or functionality is working properly. It’s a narrow, focused form of regression testing.
✅ Example: After fixing login issue, tester checks only login module.
🔹 77. What is Regression Testing?
Regression testing ensures that recent code changes haven't broken the existing functionalities. It verifies the overall system stability.
✅ Tip: Performed after every code change or release.
🔹 78. What is Retesting?
Retesting is the process of testing the same test case again after fixing a defect to ensure the bug is actually resolved.
✅ Focus: Only the failed test cases are executed again.
🔹 79. What is a Test Environment?
A test environment includes hardware, software, and network configuration where testers run tests. It should resemble the production environment as closely as possible.
✅ Includes: Server, OS, database, browsers, etc.
🔹 80. What is a Test Lab?
A test lab is a controlled and isolated environment where testers perform various types of testing. It includes all necessary tools and systems required.
✅ Goal: Simulate production without impacting real users.
🔹 81. What is Compatibility Testing?
Compatibility testing checks whether the application works properly across different browsers, OS, devices, and network environments.
✅ Example: Testing a website in Chrome, Firefox, Safari, etc.
🔹 82. What is Usability Testing?
Usability testing evaluates the software’s user interface and user experience. It checks if the app is easy to use and intuitive.
✅ Involves: Real users performing real tasks.
🔹 83. What is GUI Testing?
GUI testing focuses on checking graphical elements like buttons, icons, menus, and layouts. It ensures they work and look as expected.
✅ Checks: Font size, alignment, colors, behavior.
🔹 84. What is Compliance Testing?
Compliance testing ensures that the application meets industry standards, regulations, or laws. It’s important in healthcare, finance, etc.
✅ Example: GDPR, HIPAA compliance.
🔹 85. What is Internationalization Testing?
Internationalization testing checks whether the application can be adapted to different languages and regions without code changes.
✅ Goal: Ensure support for global use.
🔹 86. What is Localization Testing?
Localization testing checks if the application works correctly in a specific region or language. It includes date format, currency, translation, etc.
✅ Example: Showing ₹ in India and $ in the US.
🔹 87. What is Recovery Testing?
Recovery testing checks how well the system recovers after a crash, failure, or unexpected shutdown.
✅ Goal: Ensure data safety and system stability after failure.
🔹 88. What is Installation Testing?
Installation testing ensures the software installs and uninstalls properly in different environments without issues.
✅ Includes: Setup, configuration, uninstallation.
🔹 89. What is Mutation Testing?
Mutation testing involves modifying the program’s code slightly to check if the test cases catch the changes. It helps measure test effectiveness.
✅ If tests fail: Tests are good.
🔹 90. What is A/B Testing?
A/B testing compares two versions of an application to determine which performs better. Common in marketing and UI optimization.
✅ Used in: Web design, product experiments.
🔹 91. What is Static Testing?
Static testing involves reviewing documents, code, or requirements without executing the program.
✅ Example: Reviewing code, walkthroughs, peer reviews.
🔹 92. What is Dynamic Testing?
Dynamic testing involves executing the code and checking the application behavior.
✅ Includes: Unit, system, integration testing.
🔹 93. What is Monkey Testing?
Monkey testing is random testing done without test cases to try and break the system.
✅ Example: Random clicks, inputs by a tester.
🔹 94. What is Exploratory Testing?
Exploratory testing is where testers learn the application and design tests on the fly. It's based on tester creativity and experience.
✅ Useful when: No time for scripted testing.
🔹 95. What is Session-Based Testing?
Session-based testing is a structured way of exploratory testing, performed in time-boxed sessions with clear goals.
✅ Report: Includes session notes and test coverage.
🔹 96. What is Ad Hoc Testing?
Ad hoc testing is unplanned testing done without any documentation or plan to break the system randomly.
✅ Goal: Discover defects missed in formal testing.
🔹 97. What is Grey Box Testing?
Grey box testing is a mix of white box and black box testing. The tester has partial knowledge of the internal workings.
✅ Example: API testing with known request/response format.
🔹 98. What is Manual Testing Lifecycle?
It includes requirement analysis → test planning → test case design → environment setup → test execution → defect logging → test closure.
✅ A structured flow for manual QA.
🔹 99. What is a Bug Life Cycle?
The bug life cycle describes the stages a defect goes through from discovery to closure: New → Assigned → Open → Fixed → Retested → Closed/Rejected.
✅ Tracks progress and ownership.
🔹 100. What is a Severity vs Priority in Defect?
-
Severity: Impact of the bug on the application
-
Priority: Urgency of fixing the bug✅ Example: Login failure = High severity & priority
🔹 101. What is Load Testing?
Load testing checks how the system behaves under expected user load. It identifies performance bottlenecks and ensures the app can handle user traffic.
✅ Example: Testing a website with 1000 simultaneous users.
🔹 102. What is Stress Testing?
Stress testing pushes the system beyond normal limits to see how it handles high traffic or low resources. It checks system stability under extreme conditions.
✅ Goal: Find system breaking point.
🔹 103. What is Volume Testing?
Volume testing examines system performance by increasing the amount of data. It checks how the app handles large volumes of data over time.
✅ Example: Uploading 10GB of data into a database.
🔹 104. What is Spike Testing?
Spike testing suddenly increases the number of users or load on the system to check how it reacts and recovers.
✅ Used for: Testing unpredictable traffic surges.
🔹 105. What is End-to-End Testing?
End-to-end testing validates the entire application workflow from start to finish to ensure everything works together as expected.
✅ Covers: UI, backend, database, API integration.
🔹 106. What is Benchmark Testing?
Benchmark testing compares the system performance against industry standards or previous versions.
✅ Focus: Speed, memory, efficiency.
🔹 107. What is Code Review?
Code review is a static testing technique where developers examine each other's code to find errors, improve quality, and ensure standards are met.
✅ Benefits: Early defect detection.
🔹 108. What is Smoke Testing vs Sanity Testing?
-
Smoke: Basic testing to check if the build is stable.
-
Sanity: Targeted testing to verify specific functionality.✅ Tip: Smoke = wide, Sanity = deep.
🔹 109. What is Integration Testing?
Integration testing checks the interaction between integrated modules to ensure they work together as expected.
✅ Done after: Unit testing.
🔹 110. What is Unit Testing?
Unit testing involves testing individual components or functions in isolation to ensure they work correctly. Usually done by developers.
✅ Tool: JUnit, NUnit.
🔹 111. What is Test Harness?
Test harness is a set of tools and test data used to test software components in isolation. It includes drivers and stubs.
✅ Helps: Automate test execution.
🔹 112. What is Test Bed?
Test bed is a configured hardware and software environment used to perform testing. It includes OS, network, database, and testing tools.
✅ Like: A mini setup for testing.
🔹 113. What is Test Script?
Test script is a set of instructions written for automation or manual execution to validate a feature or functionality.
✅ In automation: Written in tools like Selenium, QTP.
🔹 114. What is Error Guessing?
Error guessing is a test design technique where the tester uses experience to guess areas likely to have bugs.
✅ Example: Entering negative numbers in quantity field.
🔹 115. What is Boundary Value Analysis?
Boundary Value Analysis (BVA) is a test design technique that focuses on values at the edges of input ranges.
✅ Example: Age field = 17, 18, 19 if valid range is 18–60.
🔹 116. What is Equivalence Partitioning?
Equivalence Partitioning divides input data into valid and invalid partitions and tests one value from each partition.
✅ Reduces: Number of test cases.
🔹 117. What is Decision Table Testing?
Decision table testing is used to test combinations of inputs and their associated actions based on rules.
✅ Good for: Business rules and conditions.
🔹 118. What is State Transition Testing?
State transition testing checks how the system behaves for different inputs in different states.
✅ Example: ATM states – card inserted, PIN entered, money withdrawn.
🔹 119. What is Use Case Testing?
Use case testing validates scenarios that users perform with the system, usually covering real-world flows.
✅ Focus: Functional paths followed by end users.
🔹 120. What is Test Summary Report?
A test summary report includes testing objectives, efforts, test results, defect metrics, and conclusions about product quality.
✅ Shared with: Managers and stakeholders.
🔹 121. What is Entry and Exit Criteria in Testing?
-
Entry: Conditions needed to begin testing (e.g., environment setup done).
-
Exit: Conditions to stop testing (e.g., all critical bugs fixed).✅ Helps define test milestones.
🔹 122. What is Verification vs Validation?
-
Verification: Are we building the product right? (Documents, design)
-
Validation: Are we building the right product? (Actual software)✅ Verification = static, Validation = dynamic.
🔹 123. What is Test Management Tool?
A test management tool helps plan, track, and manage test cases, execution, and reporting.
✅ Examples: TestRail, Zephyr, Quality Center.
🔹 124. What is Test Execution?
Test execution is the process of running test cases and comparing actual results with expected results.
✅ Done after: Test planning and design.
🔹 125. What is Release Note?
A release note is a document shared with stakeholders after a software release, detailing new features, fixes, known issues, and environment info.
✅ Helps users understand what’s new.
🔹 126. What is a Test Strategy?
A test strategy defines the overall approach and objectives for software testing, including test levels, techniques, tools, and risk management.
✅ Used by: Project managers and QA leads.
🔹 127. What is a Test Plan?
A test plan is a document that outlines the scope, objectives, resources, schedule, and activities of testing.
✅ Includes: Test items, tasks, environment, roles.
🔹 128. What is a Traceability Matrix?
Traceability Matrix maps test cases to requirements to ensure complete test coverage.
✅ Helps track: Requirement coverage and test execution.
🔹 129. What is a Test Case?
A test case is a set of conditions or steps used to verify a particular feature or functionality of an application.
✅ Includes: Input, expected result, actual result.
🔹 130. What is a Test Scenario?
A test scenario is a high-level idea of what to test, covering multiple test cases under one flow.
✅ Example: Login functionality scenario.
🔹 131. What is a Test Condition?
A test condition is a specific situation or state that must be tested to verify an application works as expected.
✅ Derived from: Requirements or design.
🔹 132. What is a Test Data?
Test data is the input data used to execute test cases. It can be valid, invalid, or edge case data.
✅ Types: Static or dynamic data.
🔹 133. What is a Defect Report?
A defect report documents the issue found during testing, including steps to reproduce, expected vs actual results, and severity.
✅ Tools: Jira, Bugzilla.
🔹 134. What is a Defect Density?
Defect density measures the number of defects per unit of code (e.g., per 1000 lines).
✅ Helps measure: Code quality.
🔹 135. What is Severity in Testing?
Severity defines how badly a defect impacts the application’s functionality.
✅ High severity: System crash.
🔹 136. What is Priority in Testing?
Priority indicates how quickly a defect should be fixed.
✅ High priority: Critical business feature broken.
🔹 137. What is a Test Closure Report?
Test closure report is prepared at the end of testing phase. It summarizes test coverage, defect details, lessons learned, and final product status.
✅ Useful for: Stakeholder communication.
🔹 138. What is a Test Metric?
Test metrics are measures used to assess the efficiency, effectiveness, and quality of the testing process.
✅ Examples: Test case pass rate, defect density.
🔹 139. What is Risk-Based Testing?
Risk-based testing prioritizes testing based on the risk of failure and its impact on the business.
✅ Focuses on: Critical areas first.
🔹 140. What is Agile Testing?
Agile testing is a continuous testing approach in agile development where testing starts early and is integrated throughout the lifecycle.
✅ Works with: Sprints and user stories.
🔹 141. What is Sprint in Agile?
A sprint is a time-boxed iteration (usually 2–4 weeks) during which a specific set of features is developed and tested.
✅ Used in: Scrum framework.
🔹 142. What is Scrum?
Scrum is an agile framework that organizes work into sprints and includes roles like Scrum Master, Product Owner, and team members.
✅ Meetings: Daily standups, sprint reviews.
🔹 143. What is Kanban?
Kanban is a visual workflow management method using boards and cards to manage work in progress.
✅ Focus: Continuous delivery and limiting work-in-progress.
🔹 144. What is a Daily Standup?
Daily Standup is a short team meeting where each member shares what they did yesterday, what they plan today, and any blockers.
✅ Time: 15 minutes max.
🔹 145. What is Retrospective Meeting?
A retrospective is held at the end of a sprint to reflect on what went well, what didn’t, and how to improve.
✅ Goal: Continuous improvement.
🔹 146. What is UAT?
User Acceptance Testing (UAT) is done by end users to confirm the system meets their business needs and is ready for production.
✅ Last phase before go-live.
🔹 147. What is Production Testing?
Production testing is done after deployment to ensure the software is working properly in the live environment.
✅ Also called: Post-release validation.
🔹 148. What is Defect Triage?
Defect triage is a process where defects are reviewed, prioritized, and assigned to appropriate developers based on severity and impact.
✅ Involves: QA, dev, and PMs.
🔹 149. What is Test Driven Development (TDD)?
TDD is a development practice where tests are written before the code to ensure functionality is built as expected.
✅ Cycle: Write test → Write code → Refactor.
🔹 150. What is Behavior Driven Development (BDD)?
BDD extends TDD by writing test scenarios in natural language, helping collaboration among developers, testers, and business teams.
✅ Tools: Cucumber, SpecFlow.
🔹 151. What is a bug life cycle?
Bug life cycle refers to the various stages a defect goes through during its lifetime.
✅ Stages: New → Assigned → Fixed → Retest → Closed.
🔹 152. What is defect severity and who decides it?
Severity is the impact level of a defect on the system. It is usually decided by the QA engineer.
✅ High severity: System crash or data loss.
🔹 153. What is defect priority and who decides it?
Priority tells how soon a defect should be fixed. It’s usually decided by the project manager or client.
✅ High priority: Blocking key features.
🔹 154. What is exploratory testing?
Testing without predefined test cases, where testers explore the application on the fly.
✅ Goal: Find unexpected issues quickly.
🔹 155. What is monkey testing?
Monkey testing is random testing without any plan or strategy to check system stability.
✅ Good for: Stress and crash testing.
🔹 156. What is sanity testing?
Sanity testing checks that recent changes haven’t broken basic functionality.
✅ Quick check: Focused and narrow.
🔹 157. What is regression testing?
Regression testing ensures that new code changes haven’t affected existing features.
✅ Important after: Bug fixes and updates.
🔹 158. What is re-testing?
Re-testing is testing the same bug again after it has been fixed.
✅ Different from: Regression testing.
🔹 159. What is static testing?
Static testing involves checking documents, code, or design without executing the code.
✅ Examples: Reviews, walkthroughs.
🔹 160. What is dynamic testing?
Dynamic testing involves executing the code to validate the output against the expected result.
✅ Example: Running test cases on the application.
🔹 161. What is boundary value analysis (BVA)?
BVA is a black-box technique that tests the boundary values of input ranges.
✅ Example: Min, max, just inside/outside boundaries.
🔹 162. What is equivalence partitioning?
Equivalence partitioning divides input data into valid and invalid classes to reduce test cases.
✅ Used for: Effective test coverage.
🔹 163. What is decision table testing?
It’s a technique that uses tables to represent different combinations of inputs and their expected outputs.
✅ Helps with: Complex business logic.
🔹 164. What is state transition testing?
Testing that checks the system’s response to different state changes based on inputs.
✅ Example: Login attempts with different statuses.
🔹 165. What is error guessing?
Testers use their experience to guess possible errors and test for them.
✅ Based on: Intuition and domain knowledge.
🔹 166. What is a use case?
A use case describes how a user will interact with the system to achieve a goal.
✅ Used to: Derive test scenarios.
🔹 167. What is compatibility testing?
It checks how well the application works across different devices, browsers, or OS.
✅ Example: Chrome vs Firefox behavior.
🔹 168. What is globalization testing?
It ensures the software works in multiple regions with different languages or currencies.
✅ Focus on: Locale-based behavior.
🔹 169. What is localization testing?
Checks that the software content is adapted correctly for a specific region or language.
✅ Example: Date, time, currency format.
🔹 170. What is recovery testing?
It tests how well the system recovers from crashes, hardware failures, or power loss.
✅ Important for: Banking and healthcare apps.
🔹 171. What is install/uninstall testing?
It checks the smooth installation and uninstallation process of an application.
✅ Includes: Setup errors, registry cleanup.
🔹 172. What is maintainability testing?
This testing checks how easy it is to maintain the software in terms of updates and bug fixes.
✅ Also includes: Readability and structure of code.
🔹 173. What is reliability testing?
It ensures the software performs consistently under defined conditions for a specific time.
✅ Focus on: Stability over time.
🔹 174. What is performance testing?
It checks the speed, responsiveness, and stability of the system under load.
✅ Tools: JMeter, LoadRunner.
🔹 175. What is stress testing?
It tests how the system behaves under extreme conditions beyond its capacity.
✅ Goal: Identify breaking point.
🔹 176. What is spike testing?
Spike testing evaluates how the system handles sudden increases or drops in user load.
✅ Example: Sudden traffic surge on an e-commerce site.
🔹 177. What is volume testing?
Volume testing checks the system's ability to handle large amounts of data.
✅ Focus: Database performance and data limits.
🔹 178. What is scalability testing?
It tests how well a system can grow in size or capacity without performance loss.
✅ Used for: Planning infrastructure expansion.
🔹 179. What is usability testing?
Usability testing ensures the application is easy to use and user-friendly.
✅ Focus: User satisfaction and navigation.
🔹 180. What is compliance testing?
This testing checks if the software meets regulatory or legal standards.
✅ Example: GDPR or HIPAA compliance.
🔹 181. What is accessibility testing?
Accessibility testing ensures the app is usable by people with disabilities.
✅ Tools: JAWS, NVDA.
🔹 182. What is configuration testing?
It tests the software under different hardware and software configurations.
✅ Goal: Identify environment-specific issues.
🔹 183. What is UI testing?
UI testing checks the user interface elements like buttons, fonts, colors, and layout.
✅ Focus: Consistency and design quality.
🔹 184. What is smoke testing?
Smoke testing is a quick test to ensure the basic functionality of the application is working.
✅ Also called: Build verification testing.
🔹 185. What is ad-hoc testing?
Ad-hoc testing is an informal, unstructured testing done without test cases.
✅ Goal: Find bugs using creativity and intuition.
🔹 186. What is negative testing?
Negative testing checks the system's behavior with invalid or unexpected inputs.
✅ Example: Entering text in a numeric field.
🔹 187. What is positive testing?
Positive testing verifies the system with valid and expected input.
✅ Goal: Ensure correct functionality.
🔹 188. What is test strategy?
Test strategy is a high-level document that outlines the testing approach, goals, and scope.
✅ Created by: Test managers.
🔹 189. What is test plan?
Test plan is a document that defines the objectives, resources, schedule, and scope of testing.
✅ Includes: Test cases, tools, roles, risks.
🔹 190. What is test case?
A test case is a set of conditions or steps to verify a specific feature or function.
✅ Parts: Input, steps, expected result.
🔹 191. What is test scenario?
A test scenario is a high-level idea of what needs to be tested.
✅ Example: Verify login functionality.
🔹 192. What is test data?
Test data refers to the input used to perform testing on the application.
✅ Types: Valid, invalid, boundary, null.
🔹 193. What is defect density?
Defect density is the number of defects found per size of the software component (e.g., per 1,000 lines of code).
✅ Used for: Quality analysis.
🔹 194. What is traceability matrix?
Traceability matrix is a document that maps requirements to test cases.
✅ Goal: Ensure all requirements are tested.
🔹 195. What is alpha testing?
Alpha testing is done by internal testers at the development site before releasing to customers.
✅ Focus on: Finding bugs early.
🔹 196. What is beta testing?
Beta testing is done by real users in a real environment before the final release.
✅ Used for: Gathering user feedback.
🔹 197. What is defect leakage?
Defect leakage is when a defect goes undetected in testing and is found by the end-user.
✅ Low leakage: Indicates good testing.
🔹 198. What is test environment?
A test environment is a setup of software and hardware where testing is executed.
✅ Includes: Servers, databases, tools.
🔹 199. What is end-to-end testing?
End-to-end testing verifies a complete flow of an application from start to finish.
✅ Example: From login to payment confirmation.
🔹 200. What is manual testing?
Manual testing is the process of manually checking the application for defects without using automation tools.
✅ Involves: Human effort, test cases, reports.
Congratulations! You now have 200 Manual Testing Interview Questions and Answers in simple, easy-to-remember language. Perfect for interviews and revision!
Best of luck for the Interview