What is a Test Case?

A test case is a set of steps that you follow to check if

something in the app is working correctly.
What is a Test Scenario?
A test scenario is a big idea or situation you want to
check in your app. It tells what to test but not the
detailed steps.
What is a Test Plan?
A test plan is a document that explains how testing will
be done for a project or feature. It includes what to test,
who will test, when, and how.

Types of Testing:
Manual Testing — Testing by hand without tools.
Automation Testing — Using tools/scripts to test
automatically.
Functional Testing — Check if the features work as
expected.
Non-Functional Testing — Check things like speed,
security, usability.
Unit Testing — Test small parts (like functions) of the
code.
Inte…
What is User Acceptance Testing (UAT)?
User Acceptance Testing means real users test the app to
check if it works the way they need.
======
What is an Environment in Testing?
An environment is the place or setup where we test the
app.
===
Types of Environments (in Simple English):
Development Environment

Where developers build and write code.

Testing Environment
Where testers check if the app works correctly.
Staging Environment
A copy of the real app; used for final testing before
release.
Production Environment
The live app that real users use.
UAT Environment (User Acceptance Testing)
Where real users test the app before it goes live.
Integration Environment
Where different parts of the app are tested together.

=======
What is Verification in Manual testing?
Verification means checking if the app is built correctly
according to the requirements.
==========
== Bug life cycle steps in manual testing
New – Tester finds a bug and reports it.
Assigned – Bug is assigned to a developer.
Open – Developer starts working on it.
Fixed – Developer fixes the bug.
Retest – Tester checks if the bug is really fixed.
Closed – Bug is gone, and tester confirms it’s fixed.
Reopen – If the bug is still there, it’s reopened.
Rejected – Developer says it’s not a bug or not valid.
Deferred – Bug will be fixed later, not now.
==================
> What is STLC/ Explain the Software Testing Life Cycle
(STLC).

STLC stands for Software Testing Life Cycle.

🧪 STLC Steps (Simple and Easy):

Requirement…
Distinguish between functional and non-functional
testing.
✅ Functional Testing
Checks what the app does
Tests features and actions
Example: Can you log in? Can you book a car?

✅ Non-Functional Testing
Checks how the app works
Tests speed, security, and performance
Example: Is the app fast? Is it safe to use?
==============
How do you write a good test case? Discuss attributes of
a good test case.
✅ How to Write a Good Test Case:
1. Understand Requirements
Read what the app should do.
2. Write Clear Steps
Describe exactly what to do to test.
3. Define Expected Result
Say what should happen after each step.
4. Keep it Simple
Use easy language anyone can understand.
5. Be Specific
Test one thing at a time.

✅ Attributes of a Good Test Case:

Clear and Simple: Easy to re…
What is the Role of a Test Engineer in Manual Testing:
A test engineer checks the app by hand to make sure it
works correctly.
🔹 What they do:
Read what the app should do
Write test steps
Test the app step by step
Find and report any bugs
Test again after bugs are fixed
Share test results with the team

1. Regression testing

Regression testing is the process of testing changes to

Applications to make sure that the existing application still
works with the new changes.
Automation testing majorly does Regression testing
Recommended before every release
Effective Regression Tests can be done by selecting the
following test cases –
Test cases which have frequent defects
Functionalities Critical
Integration Test Cases

2. Smoke tests
Smoke test development and regression test development are
related and similar,
The only difference is in depth scope and duration of running
the tests
Typically Runs after every build
Add the most critical tests to the smoke test suite
Automate smoke testing in your CD environment

3. Component Testing
Component testing is a method where testing of each component
in an application is done separately.
Component testing may be done in isolation from rest of the
system depending on the development life cycle model chosen
for that particular application.
Difference between Component Test and Unit Test

4. What is Integration Testing?

Integration Testing is defined as a type of testing where software
modules are integrated logically and tested as a group.

5. System/EndtoEnd Testing:
SYSTEM TESTING is a level of software testing where a
complete and integrated software is tested. The purpose of this
test is to evaluate the system's compliance with the specified
requirements

6. Exploratory Testing :
Exploratory testing is an unscripted QA testing technique used
to discover unknown issues during and after the software
development process
Automation testing has few limits and this exploratory testing is
essential to deliver product with bug free confidence
Difference Between Verification and Validation :
Verification :The process of evaluating work-products (not the
actual final product) of a development phase to determine
whether they meet the specified requirements for that phase..
Validation : The process of evaluating software during or at the
end of the development process to determine whether it satisfies
specified business requirements.
UAT Testing: This is typically the last step before the product
goes live or before the delivery of the product is accepted. UAT
is after the product itself is thoroughly tested
****************************************************
****************************************************
******************************
Load Testing : Load Testing help us to study the behavior of the
application under various loads. The main parameter to focus is
response time. This study reveals how many concurrent users
that server can handle effectively and quickly.
Stress Testing : Stress Testing help us to observe the stability of
the application. The main intention is to identify the breaking
point of the server

=====Interview Question--------------------------------

Suppose you find a bug in production. how would you

make sure that the same bug is not introduced again?
Add uncaught functionality to regression test cases If you
have Automated Regression Suite, then write a new Script
which validates above functionality
What do you do when your developer denies that what
you filed IS A BUG?

Provide Business Documentation reference to support

why the existing functionality is not as per design.

Involve Product Owner / Business Analyst for Discussion.

IF Bug is not reproducible then

Provide Screenshots of the Bug, Give Timestamp on

when you reproduced this so that Developer can check in
Application Logs.

1 Provide Test Data you have used for replicating issue

What has been one of your greatest challenges while

doing regression testing?

Test Data issue

Improper selection of regression test cases might skip a

major regression defect to be found
Difference between functional and non-functional
testing?

Functional testing verifies that features/System working

as expected according to requirements,

Nonfunctional requirements: How Well the system does it

within design & resource constraints

Enlist some of the key challenges that are faced while

performing Software Testing

Data Issues,

Environment Available,

Using right set of tools

What are the different levels of testing?

Unit Testing

Integration Testing

System Testing

Acceptance Testing
: What are the drawbacks of the Agile
implementation/ methodology that you faced?

Sprints are usually very deadline constrained.

Documentation is not the priority

Frequent change in requirements

What is your approach when you have a high priority

release to be delivered in a very short time?

Run Automation Suites

. Run Unit tests.

Manual testing on high level Priority Business test cases

Give an example for High Priority Low Severity Bug

Wrong Logo Image in Application

What is your understanding regarding a Test plan?

test plan is a document that consists of scope, approach,
resources, and outline of the testing project as well as the
activities for tracking the progress of the project.
Explain what will be your reaction if a project you had
been working got Sudden change in its deadline?

As a QA Engineer, Be open on your thoughts if you can

deliver the project with QA Sign off covering all testcases

If Pre release is must, then discuss the oppurtunities of

increasing QA Resources or possibility of partial product
delivery.

You have the power to hold QA Sign off if you are not
satisfied with quality of product which eventually stops
the release date
What is the difference between Smoke testing and
Sanity Testing?

Sanity testing is a kind of Software Testing performed

after receiving a software build, with minor changes in
code, or functionality, to ascertain that the bugs have been
fixed and no further issues are introduced due to these
changes.
Smoke Testing is a special type of testing performed on
Software build to check the critical functionalities of the
program
If a small section of code in application is updated?

What is your Test approach in validating it?

Ad-hoc Testing and Exploratory Testing?

Adhoc testing Includes learning the application first and

then proceeding with the testing process.

Exploratory testing form of testing includes learning the

application while testing.

What kind of testing focuses on how an application

behaves under heavy user load, such as 3000 users
accessing an API simultaneously?

Ans - Performance Testing

Performance testing, which includes stress and load

testing, assesses an application's stability, responsiveness,
and resource usage when subjected to a high volume of
concurrent users or transactions.

========Interview Question============
Fundamentals & Core Concepts
1. What is Manual Testing?
Testing performed by humans executing test cases
without automation, leveraging intuition to catch
anomalies. GeeksforGeeksWikipedia
2. Manual Testing vs Test Automation
Manual uses human execution; automation uses
scripts/tools to execute tests repeatedly.
GeeksforGeeksWikipedia
3. Advantages of Manual Testing
Ideal for GUI, exploratory, and usability tests; easy
to start and flexible. GeeksforGeeks
4. Drawbacks of Manual Testing
Time-consuming, prone to human error, and
inconsistent in execution. GeeksforGeeks
5. What is QC (Quality Control)?
Product-focused, defect-finding process executed
by testers. GeeksforGeeks
6. Explain SDLC
Phases include Requirements → Design →
Development → Testing → Deployment →
Maintenance. GeeksforGeeks
7. Explain STLC
Involves Requirement Analysis → Test Planning
 → Test Case Development → Environment Setup
→ Execution → Closure. QA Nextgen
8. What is a Test Case?
A document containing steps, input data, and
expected results to test functionality.
9. What is a Test Scenario?
High-level objective of what needs to be tested,
often derived from requirements.
10. Difference between Bug, Defect, Error
An error is a human mistake; a defect is found
during testing; a bug is a defect logged for fixing.

Test Documentation & Coverage

11. What is Test Plan?
Document detailing the scope, approach,
resources, and schedule of testing. GeeksforGeeksmindmajix
12. What is a Traceability Matrix (RTM)?
Maps requirements to test cases to ensure complete
coverage. cloudsoftsol.comTutorialKart
13. What is Test Coverage?
Measure of how much of the application
(requirements or code) is tested. TutorialKartmindmajix
14. Is 100% Test Coverage Possible?
Rarely feasible; focus instead on high-risk and
critical areas. mindmajixtekslatetutor
 15. What is a Test Suite?
A collection of related test cases grouped by
functionality or module.
16. What is Test Execution?
Process of running test cases and logging results
and defects.
17. What is Test Closure?
Summarizes all testing activities, results, coverage,
and lessons learned. GeeksforGeeks
18. What is a Test Oracle?
Source of expected outcomes (e.g., spec
documents, previous versions). Hello Intern
19. What is Test Data?
Input values used to run test cases, documented
separately for reusability. GeeksforGeeks
20. What is a Bug Report?
Structured record of a defect including steps,
environment, severity, and screenshot.

Testing Techniques & Types

21. What is Regression Testing?
Re-running test cases to ensure changes don’t
break existing features. softwaretesttips.comGeeksforGeeks
22. Retesting vs Regression Testing
Retesting checks specific bug fixes; regression
 ensures unchanged functionality still works.
GeeksforGeeks
23. What is Smoke Testing?
Quick check of core functionality to verify build
stability. softwaretesttips.com
24. What is Sanity Testing?
Focused check to confirm recent changes work as
intended. softwaretesttips.com
25. What is Exploratory Testing?
Simultaneous test design and execution driven by
tester insight. hiration.com
26. What is Ad Hoc Testing?
Informal, unstructured testing to discover defects
quickly. softwaretesttips.com
27. What is Boundary Value Analysis?
Tests values at input boundaries to catch edge-case
defects. softwaretesttips.com
28. What is Equivalence Partitioning?
Dividing inputs into groups that behave similarly
to reduce test cases.
29. What is Risk-Based Testing?
Prioritizing tests based on risk impact and
probability. innovateqa.com
30. What is TDD?
Write tests before code; ensures early validation
and better code design. hiration.com
Integration & Testing Levels
31. Top-Down Integration Testing
Test higher modules first, using stubs for lower
ones. tekslatetutor
32. Bottom-Up Integration Testing
Begin with lower modules, using drivers for higher
ones.
33. Hybrid Integration Testing
Combination of top-down and bottom-up
approaches. tekslatetutor
34. Unit, System & Acceptance Testing
Unit: parts; System: whole system; Acceptance:
meets user needs. Reddittekslatetutor
35. Functional vs Non-Functional Testing
Functional: features; Non-Functional:
performance, usability, security.
36. Compatibility Testing
Testing across browsers, OS, and devices.
cloudsoftsol.com
37. Usability Testing
Check user-friendliness and navigation clarity.
38. Accessibility Testing
Ensure the app works for users with disabilities.
cloudsoftsol.com
 39. Localization vs Globalization Testing
Localization: locale-specific; Globalization:
adaptability across regions. tekslatetutor
40. Baseline Testing
Use performance benchmarks for future
comparison.

Defects & Process Management

41. Defect Life Cycle
New → Assigned → Fixed → Tested → Closed
(or Reopened). softwaretesttips.com
42. Defect Cascading
One defect causing subsequent defects in other
areas. tekslatetutor
43. Defect Triage
Prioritize defects in team sessions based on impact
and severity.
44. Severity vs Priority
Severity: how bad; Priority: how soon it should be
fixed. GeeksforGeeks
45. Entry & Exit Criteria
Conditions required before starting or ending a
testing phase. cloudsoftsol.com
 46. Defect Leakage
Bugs escaping to production; prevent via thorough
regression. cloudsoftsol.com
47. Handling Non-Reproducible Bugs
Gather logs, environment info, screenshots, and
reproduce consistently. cloudsoftsol.com
48. Handling Changing Requirements
Update test cases, reprioritize, and communicate
clearly.
49. Root Cause Analysis (RCA)
Techniques like “5 Whys” or Fishbone to identify
defect origins. TutorialKart
50. Test Strategy vs Test Plan
Strategy: high-level approach; Plan: detailed
execution steps. Wikipedia

Tools, Environments & Roles

51. Bug Tracking Tools
e.g., JIRA, Bugzilla. Hello Intern
52. Test Management Tools
e.g., TestRail, Zephyr, HP ALM. Hello Intern
53. Testing Environments
Development, Test, Staging, Production. Hello
Intern
54. Test Harness vs Test Bed
Harness: support for test execution; Bed:
configured test environment. GeeksforGeeks
55. What is Black-Box Testing?
Testing without knowledge of internal structure.
QA Nextgen
56. What is Static Testing?
Reviews and walkthroughs without code
execution. tekslatetutor
57. Role of a Manual Tester
Design, execute tests, log defects, and maintain
documentation.
58. Key Qualities of a Good Tester
Attention to detail, analytical thinking,
communication skills.
59. Test Pyramid Concept
Structure prioritizing unit tests, then integration,
then UI.
60. Continuous Testing Role
Integrating manual sanity tests within automated
CI/CD pipelines. Wikipedia
Scenario-Based & Behavioral
61. How many test cases per day?
Varies by complexity; estimate based on steps,
clarity, and domain. GeeksforGeeks
62. How do you derive test cases?
From requirements, use cases, and user stories.
GeeksforGeeks
63. What if documentation is missing?
Use exploratory testing, interview stakeholders,
document assumptions. cloudsoftsol.com
64. Testing a Login Page?
Test valid/invalid credentials, session timeout,
SQLi, UI elements. cloudsoftsol.com
65. Handling rejected bugs?
Provide solid repro steps, evidence, and escalate if
necessary. scriptng.com
66. Prioritizing test cases?
Based on risk, business value, and impact.
scriptng.com
67. Regression Purpose?
Ensure new changes didn’t break existing features.
scriptng.com
68. Handling time constraints?
Test critical paths, recent changes, and
communicate risks. scriptng.com
69. Exploratory Testing Definition?
Structured chaos—test based on charters and
observations. scriptng.com
70. Behavioral: Handling conflict?
Communicate data-driven impact, seek
collaboration, stay professional. scriptng.com
71. Agile Testing Approach
Frequent releases, constant feedback, cross-
functional collaboration.
72. API Testing Manually
Use tools like Postman to verify request–response
and error handling.
73. Defect Density
Defects per lines of code or modules.
74. Defect Leakage
Defects found in production after release.
75. Test Execution Rate
Number of tests executed per day/time period.
76. Average Defect Age
Time from reporting to closure.
softwaretesttips.com
77. Pesticide Paradox
Repeated tests find no new bugs; update test cases
regularly.
78. 80/20 Rule in Testing
20% of test cases catch 80% of bugs.
79. AI in Manual Testing
Use for test suggestion, risk identification, or
anomaly spotting. arXiv
80. Test Closure Activities
Reporting, metric collection, retrospectives,
lessons learned.
81. Training Team Members
Peer reviews, mentoring, documentation, sharing
best practices.
82. Handling Intermittent Bugs
Add logging, test across environments, replicate
scenarios.
83. Usability Feedback
Use exploratory sessions, user observations, UI
clarity metrics.
84. Documentation Templates
Standard templates improve consistency and
onboarding.
85. Stakeholder Communication
Use dashboards, JIRA, confluence for
transparency.
86. Learning from Test Failures
Retrospectives, root cause analysis, process
improvements.
87. Continuous Learning as a Tester
Stay updated with tools, domain knowledge,
methodologies.
88. Peer Reviews in Testing
Improve quality of test scripts and defect reports.
89. Test Strategy Creation
Define risk areas, test types, environment needs,
and test approach.
90. Scalability in Manual Testing
Prioritize wisely, reuse test assets, make templates.
91. Conflict with Developers?
Use empathy, data evidence, focus on user
outcomes.
92. Handling Remote Testing Teams
Clear roles, regular syncs, shared documentation.
93. Security Smoke Tests
Simple SQL injection or unauthorized access
checks.
94. Change Management in Testing
Version control test artifacts, retest updated
features.
95. Test Environment Parity
Match prod configurations, use virtualization or
containers.
96. Risk Mitigation in Test Strategy
Identify high-risk areas and test early and often.
 97. Session-Based Testing
Time-boxed exploratory testing sessions tracked
with charters.
98. Test Metrics Value
Aid in decision-making, identifying trends, and
improving process.
99. Final Sign-Off Responsibilities
Review results, close open defects, assess release
readiness.
100. Future Trends
Emphasis on accessibility, AI, and remote testing
practices in 2025.
101. ===============

1. What is Manual Testing?

Answer: Manual testing is the process of manually
executing test cases without using automation tools to
identify defects in software. It helps ensure software
quality by simulating real user behavior.

2. What are the different types of manual

testing?
Answer: Common types include Functional Testing,
Regression Testing, Smoke Testing, Sanity Testing,
Exploratory Testing, Ad-hoc Testing, Usability Testing,
and Acceptance Testing.

3. What is the difference between Manual

Testing and Automation Testing?
Answer: Manual testing is performed by humans and
is best for exploratory and usability testing.
Automation testing uses scripts and tools to run tests
faster and repeatedly, ideal for regression and load
tests.

4. Explain SDLC and STLC.

Answer:
 SDLC (Software Development Life Cycle):
Phases involved in software development from
requirement gathering to deployment and
maintenance.
 STLC (Software Testing Life Cycle): Phases
specific to testing — requirement analysis, test
planning, test case design, test execution, defect
reporting, and test closure.
5. What is a Test Case? What does it
include?
Answer: A test case is a documented set of conditions,
inputs, steps, and expected results used to verify a
specific functionality or feature of an application.

6. What is the difference between a Test

Case and a Test Scenario?
Answer: A test scenario is a high-level description of
what to test, while a test case is a detailed step-by-step
procedure to test a particular aspect of the scenario.

7. What are Priority and Severity in defect

tracking?
Answer:
 Severity: Impact level of the defect on the system
(Critical, Major, Minor).
 Priority: Urgency to fix the defect (High,
Medium, Low).
8. What is Regression Testing and when is it
done?
Answer: Regression testing ensures that recent code
changes haven’t adversely affected existing
functionalities. It is done after bug fixes or new feature
additions.

9. What is the difference between Smoke

Testing and Sanity Testing?
Answer:
 Smoke Testing: Basic tests to check if the build is
stable enough for further testing.
 Sanity Testing: Focused testing to verify specific
functionality or bug fixes after receiving a stable
build.

10. What is Exploratory Testing?

Answer: Testing without predefined test cases where
testers explore the application to identify defects,
relying on experience and intuition.
11. What is Boundary Value Analysis (BVA)?
Answer: A testing technique focusing on the edge
values of input domains to catch boundary-related
defects.

12. What is Equivalence Partitioning?

Answer: Dividing input data into equivalent partitions
that are expected to be treated similarly by the software
to reduce the number of test cases.

13. What are the different levels of testing?

Answer: Unit Testing, Integration Testing, System
Testing, and User Acceptance Testing (UAT).

14. What is a Defect Life Cycle?

Answer: The journey of a defect from identification to
closure, including states like New, Assigned, Open,
Fixed, Retested, and Closed.

15. How do you write a good bug report?

Answer: A good bug report should have a clear
summary, steps to reproduce, expected vs actual
results, environment details, severity, priority, and
screenshots/logs if possible.

16. What is the difference between

Verification and Validation?
Answer:
 Verification: Checking if the product is being built
correctly (process-oriented).
 Validation: Checking if the right product is built
(product-oriented).

17. What is Test Closure? What activities are

performed?
Answer: Test Closure is the final phase where test
artifacts are archived, test summary reports are
prepared, and lessons learned are documented.

18. What are some common challenges in

Manual Testing?
Answer: Human error, time-consuming, repetitive
tasks, difficulty in covering large test cases, and lack of
tool support.
19. How do you prioritize test cases?
Answer: Based on business impact, risk, critical
functionalities, and customer usage frequency.

20. What is Monkey Testing?

Answer: Random testing with invalid or unexpected
inputs to check application stability and crash
resistance.
21. What is a Test Plan? What does it
include?
Answer: A test plan is a formal document detailing the
testing strategy, scope, objectives, resources, schedule,
deliverables, and risks related to testing.

22. What is the difference between Alpha

Testing and Beta Testing?
Answer:
 Alpha Testing: Internal testing by developers or
QA within the organization before releasing to
users.
  Beta Testing: External testing by actual users in
the real environment before official release.

23. What is the difference between Static

Testing and Dynamic Testing?
Answer:
 Static Testing: Review of documents, code, or
requirements without executing code (e.g.,
walkthroughs, inspections).
 Dynamic Testing: Actual execution of software to
validate behavior.

24. What is Usability Testing?

Answer: Testing to evaluate how user-friendly,
intuitive, and easy-to-use the application is from an
end-user perspective.

25. Explain the concept of Test

Environment.
Answer: The setup of hardware, software, network
configurations, and tools required to execute test cases
effectively.
26. What is the difference between Error,
Defect, and Failure?
Answer:
 Error: Human mistake in coding or design.
 Defect (Bug): Flaw in software that causes
deviation from expected behavior.
 Failure: When the software does not perform as
intended during execution.

27. What is Ad-hoc Testing?

Answer: Informal testing without any documentation,
performed to find defects through random checking.

28. What is Load Testing?

Answer: Testing how the system behaves under
expected load to ensure it performs well.

29. What is the difference between Test

Strategy and Test Plan?
Answer:
  Test Strategy: High-level approach and goals for
testing across projects.
 Test Plan: Detailed document for testing a specific
project or release.

30. What tools are used for manual testing?

Answer: Common tools include Jira (bug tracking),
TestRail (test case management), Bugzilla, Quality
Center, and spreadsheets for documentation.

31. What is meant by Test Coverage?

Answer: A metric that measures the amount of testing
performed by evaluating the percentage of
requirements, code, or functionalities tested.

32. What is meant by a Test Case Template?

What fields does it contain?
Answer: A standard format for documenting test cases.
Typical fields include Test Case ID, Description,
Preconditions, Test Steps, Expected Result, Actual
Result, Status, and Comments.
33. How do you handle situations when
developers disagree with your reported
defects?
Answer: Communicate clearly with evidence
(screenshots, logs), reproduce the defect, and if
necessary, involve a test lead or manager for resolution.

34. What is Risk-Based Testing?

Answer: Prioritizing testing efforts on functionalities
or areas with the highest business risk or impact.

35. What is the significance of Traceability

Matrix?
Answer: It maps requirements to test cases to ensure
all requirements are covered by testing.

36. How do you test a login page?

Answer: Test valid and invalid credentials, empty
fields, password strength, session timeouts, error
messages, and security aspects like SQL injection.
37. What is meant by a ‘Test Scenario’?
Answer: A high-level test objective that describes a
functionality or feature to be tested.

38. What is the difference between Severity

and Priority with examples?
Answer: Severity is technical impact; Priority is
business urgency.
Example: A typo (minor severity) on homepage text
may have high priority if it affects brand image.

39. What is the difference between Baseline

Testing and Sanity Testing?
Answer:
 Baseline Testing: Initial testing to set performance
benchmarks.
 Sanity Testing: Checking specific functionalities
after changes or bug fixes.
40. How do you manage test data in
manual testing?
Answer: Use realistic and relevant test data that covers
boundary and edge cases, ensuring privacy and security
compliance.

41. What is Exploratory Testing and when

should it be used?
Answer: Exploratory testing is simultaneous learning,
test design, and execution without predefined test
cases. It’s useful when requirements are incomplete or
for discovering hidden defects.

42. What is a Defect Life Cycle? Name its

stages.
Answer: The journey of a defect from identification to
closure. Stages include New, Assigned, Open, Fixed,
Retested, Reopened, Deferred, and Closed.

43. What is a Test Suite?

Answer: A collection of test cases grouped for
execution to verify a particular feature or module.
44. What are the key qualities of a good
tester?
Answer: Attention to detail, analytical thinking,
curiosity, communication skills, patience, and
persistence.

45. What is the difference between Black

Box Testing and White Box Testing?
Answer: Black box tests without knowledge of
internal code, focusing on inputs and outputs. White
box tests with full knowledge of the internal code and
structure.

46. What is Integration Testing?

Answer: Testing combined modules or components to
verify their interaction and data flow.

47. What is System Testing?

Answer: Testing the complete integrated system to
validate it against requirements.
48. What is User Acceptance Testing (UAT)?
Answer: Final testing by end users to verify the system
meets business needs before production deployment.

49. What is the difference between Positive

and Negative Testing?
Answer: Positive testing checks expected behavior
with valid inputs; negative testing checks system
response to invalid or unexpected inputs.

50. How do you prioritize test cases in

manual testing?
Answer: Based on risk, criticality, business impact,
and likelihood of failure.

51. What is the purpose of a Traceability

Matrix?
Answer: To ensure every requirement has
corresponding test cases to validate them.
52. What is the difference between Load
Testing and Stress Testing?
Answer: Load testing checks system performance
under expected load; stress testing evaluates behavior
under extreme conditions beyond normal limits.

53. What is a Test Data? How do you

prepare it?
Answer: Test data includes all inputs required for test
case execution, prepared based on requirement
specifications covering all boundary and edge cases.

54. What is a Bug Life Cycle?

Answer: See question #42; it’s the same concept
detailing defect progress.

55. How do you document test results?

Answer: Record test execution status (pass/fail), actual
results, defects found, and observations in test
management tools or documents.
56. What is Ad-hoc Testing?
Answer: Informal testing without any documentation
or planning, relying on tester’s intuition to find defects.

57. How do you hlandle a situation where a

critical bug is found just before release?
Answer: Report immediately, communicate impact to
stakeholders, help prioritize fix, and assist in retesting
before release decision.

58. What is meant by Defect Priority and

Severity? Provide examples.
Answer: Priority is urgency to fix; severity is impact
on system. For example, a crash (high severity) in
rarely used feature might have low priority.

59. How do you ensure test coverage?

Answer: By mapping test cases to requirements using
traceability matrix and covering all functional and non-
functional aspects.
60. What is Test Closure Report? What does
it include?
Answer: Final summary report including testing
activities, test metrics, defects summary, coverage,
risks, and lessons learned.

61. What is the difference between a Bug

and a Defect?
Answer: Both terms are often used interchangeably. A
bug is an error found during testing, while a defect is
any variance from the expected result, usually found in
development or post-release.

62. Explain the term “Test Coverage” and

how it is measured.
Answer: Test coverage measures how much of the
application is tested. It can be measured via
requirement coverage, code coverage, or test case
coverage.
63. What is the role of a Test Lead?
Answer: A Test Lead plans, coordinates, and monitors
testing activities, manages the team, communicates
with stakeholders, and ensures quality deliverables.

64. What are the different test case design

techniques?
Answer: Equivalence Partitioning, Boundary Value
Analysis, Decision Table Testing, State Transition
Testing, and Use Case Testing.

65. What is the difference between Static

Testing and Dynamic Testing?
Answer: Static testing involves reviews, walkthroughs,
and inspections without code execution. Dynamic
testing involves executing the software to check
functionality.

66. What is a Test Harness?

Answer: A set of tools and test data used for automated
testing, including test scripts and test execution
environments.
67. How do you report a bug? What
information should a bug report contain?
Answer: Bug reports should include a unique ID,
summary, description, steps to reproduce, expected and
actual results, severity, priority, environment,
screenshots/logs, and status.

68. What is the difference between Alpha

Testing and Beta Testing?
Answer: Alpha testing is done internally before
release, and beta testing is done by real users outside
the organization in a real environment.

69. What is Usability Testing?

Answer: Testing to assess how user-friendly, efficient,
and intuitive the application is for end users.
70. What is Test Data and why is it
important?
Answer: Test data is the input data used for testing. It’s
crucial for validating application behavior under
different conditions.

71. What is the significance of test

environment in manual testing?
Answer: It replicates the production environment to
ensure that testing is realistic and reliable.

72. What is a Test Scenario? How is it

different from a Test Case?
Answer: A test scenario is a high-level functionality to
be tested, while a test case is a detailed document with
step-by-step instructions and expected results.

73. What is Smoke Testing?

Answer: A preliminary test to check whether the basic
functions of an application are working properly.
74. What is Sanity Testing?
Answer: Focused testing to verify specific
functionality after changes or fixes.

75. What is the difference between Severity

and Priority in defect management?
Answer: Severity defines the impact of a defect on the
system; priority defines the urgency to fix the defect.

76. What are some challenges faced in

manual testing?
Answer: Time consumption, human errors, repetitive
tasks, less accuracy for complex scenarios, and
difficulty in covering large data sets.

77. How do you decide which test cases to

automate?
Answer: Automate test cases that are repetitive, time-
consuming, require multiple data sets, or need to be run
on multiple environments.
78. What is the difference between
Verification and Validation?
Answer: Verification checks if the product is being
built right; validation checks if the right product is
built.

79. What are Boundary Value Analysis and

Equivalence Partitioning?
Answer: Techniques to design test cases by testing
boundary values and grouping inputs into equivalent
classes.

80. What is End-to-End Testing?

Answer: Testing the complete flow of an application
from start to finish to ensure all integrated components
work as ex pected.

81. What is the difference between

Functional and Non-Functional Testing?
Answer:
 Functional Testing validates the software against
functional requirements (e.g., features, business
rules).
  Non-Functional Testing checks performance,
usability, reliability, security, etc.

82. What is the purpose of a Test Summary

Report?
Answer: It provides an overview of testing activities,
results, defect status, test coverage, and quality of the
build.

83. How do you estimate testing effort?

Answer: Based on the size of the application,
complexity, number of test cases, experience, and
available resources.

84. What is a Use Case Testing?

Answer: Testing based on real-world scenarios and
user actions to validate end-to-end functionality.

85. What is Defect Density?

Answer: Number of defects found per size of the
software (e.g., per 1000 lines of code).
86. What is a Test Harness?
Answer: A collection of software and test data
configured to test a program unit by running it under
varying conditions.

87. What is the difference between Re-

testing and Regression Testing?
Answer:
 Re-testing: Verifying a specific defect has been
fixed.
 Regression Testing: Checking that recent changes
have not broken existing functionality.

88. What is the importance of Requirement

Analysis in Testing?
Answer: To understand and clarify what needs to be
tested, identify testable requirements, and prepare test
conditions.

89. What is a Test Bed?

Answer: The environment configured with hardware,
software, and network to execute tests.
90. How do you handle flaky or intermittent
bugs?
Answer: Document steps carefully, try to reproduce in
different environments, increase logging, and
communicate with developers for deeper analysis.

91. What is Negative Testing? Why is it

important?
Answer: Testing with invalid inputs or unexpected
user behavior to ensure the system handles errors
gracefully.

92. What are the key components of a Test

Case?
Answer: Test case ID, description, preconditions, test
steps, expected result, actual result, status, and
remarks.
93. What is the role of a QA team in the
Software Development Life Cycle?
Answer: Ensuring software quality by planning and
executing tests, reporting defects, and validating fixes
throughout SDLC.

94. What is Boundary Value Analysis with

example?
Answer: Testing at the edges of input ranges. For input
1-10, test cases include 0,1,10,11.

95. What is meant by “Test Execution”?

Answer: Running the test cases on the application and
comparing actual results with expected outcomes.

96. What is the significance of Test Metrics?

Answer: Helps measure and track the progress and
quality of testing activities.

97. What is Compatibility Testing?

Answer: Testing software compatibility with different
browsers, OS, devices, and network environments.
98. What is Error Guessing Technique?
Answer: Using experience to guess problematic areas
in the application and design test cases accordingly.

99. What is the difference between Alpha

and Beta Testing?
Answer: Alpha testing is done by internal staff; Beta
testing is done by real users in real environments.

100. How do you deal with changing

requirements during testing?
Answer: Reassess test cases, update test plans,
communicate impact with stakeholders, and prioritize
based on business needs.

101. What is a Test Incident?

Answer: Any event during testing that requires
investigation, including unexpected results, failures, or
bugs.
102. What are the common types of
software testing documentation?
Answer: Test Plan, Test Cases, Test Scripts, Test
Summary Report, Bug Report, Traceability Matrix.

103. What is the difference between

Verification and Validation?
Answer: Verification confirms if the product is built
according to specifications (static), while validation
checks if the product meets user needs (dynamic).

104. What are the characteristics of a good

test case?
Answer: Clear, concise, comprehensive, reusable,
traceable, and includes expected results.

105. What is Decision Table Testing?

Answer: A technique that uses a table to represent
combinations of inputs and corresponding actions or
outputs.
106. What is the defect cascading
phenomenon?
Answer: When one defect leads to multiple other
defects in the system.

107. What are the differences between

Build Verification Testing (BVT) and Smoke
Testing?
Answer: They are often used interchangeably; both
verify if the build is stable enough for detailed testing.

108. What is the difference between Static

and Dynamic analysis?
Answer: Static analysis reviews code or documents
without execution; dynamic analysis involves
executing the code.

109. What is meant by Test Condition?

Answer: A testable requirement or functionality to
verify through testing.
110. What is the purpose of Defect Triage?
Answer: To prioritize and decide which defects to fix
based on severity, priority, and impact.

111. What is meant by Test Execution Cycle?

Answer: The repetitive process of running test cases,
logging defects, and retesting until quality goals are
met.

112. What are the advantages of Manual

Testing?
Answer: Flexibility, human observation, better for
usability and exploratory testing, no need for scripting
skills.
113. What is the role of a Business Analyst
in testing?
Answer: To gather requirements, clarify ambiguities,
and ensure the developed software meets business
needs.

114. What is the difference between End-to-

End Testing and System Testing?
Answer: System testing tests the complete system for
compliance with requirements, End-to-End tests full
workflow including external interfaces.

115. What is the importance of Test Data

Management?
Answer: Ensures availability of correct data for testing
while maintaining security and data integrity.

116. What is the difference between Load

Testing and Performance Testing?
Answer: Load testing checks system behavior under
expected load, performance testing measures overall
speed, responsiveness, and stability.
117. What are the types of software testing
based on execution?
Answer: Manual Testing and Automated Testing.

118. What is Configuration Management in

Testing?
Answer: Managing and controlling changes in
software and related documents during the testing
lifecycle.

119. How do you ensure effective

communication in a testing team?
Answer: Regular meetings, clear documentation, using
collaboration tools, and transparent reporting.

120. What are the common challenges

faced in Agile Testing?
Answer: Rapid changes, limited documentation,
continuous integration, and tight deadlines.
121. What is the difference between
Severity and Priority in defect
management?
Answer: Severity measures the impact of a defect on
the system, while Priority determines the order in
which a defect should be fixed based on business
needs.

122. What is the importance of a Test

Environment?
Answer: It provides a controlled setup that mimics the
production environment to ensure accurate and reliable
testing.

123. What is the difference between

Positive Testing and Negative Testing?
Answer: Positive testing checks the application with
valid inputs to verify expected behavior; negative
testing uses invalid inputs to ensure the system handles
errors gracefully.
124. What is Exploratory Testing?
Answer: An informal testing technique where testers
explore the application without predefined test cases to
identify defects.

125. How do you prioritize test cases for

regression testing?
Answer: Based on critical functionalities, recent code
changes, business impact, and areas prone to defects.

126. What is a Traceability Matrix?

Answer: A document that maps and traces user
requirements with test cases to ensure coverage.

127. What is the role of a Test Lead?

Answer: To manage and coordinate testing activities,
assign tasks, monitor progress, and communicate with
stakeholders.
128. What is the difference between Build
Verification Testing and Sanity Testing?
Answer: Build Verification Testing is a shallow, wide
test to check if the build is testable; Sanity Testing is
narrow and deep, checking specific functionality after
changes.

129. What are the different levels of

software testing?
Answer: Unit Testing, Integration Testing, System
Testing, and User Acceptance Testing (UAT).

130. What is the difference between a Test

Scenario and a Test Case?
Answer: A test scenario is a high-level concept of what
to test; a test case contains detailed steps and expected
results.

131. How do you report a defect?

Answer: Provide clear steps to reproduce, actual vs
expected results, severity, priority, environment details,
and attach screenshots or logs.
132. What is Regression Testing?
Answer: Testing existing functionalities to ensure new
changes do not break them.

133. What is Ad-hoc Testing?

Answer: Random testing without planning or
documentation to quickly find defects.

134. What is the difference between Manual

Testing and Automation Testing?
Answer: Manual testing is performed by humans
without scripts; automation uses tools and scripts to
execute tests automatically.

135. What is the Software Testing Life Cycle

(STLC)?
Answer: Phases include Requirement Analysis, Test
Planning, Test Case Development, Environment Setup,
Test Execution, and Test Closure.
136. What is the purpose of Test Closure?
Answer: To finalize testing activities, archive test
artifacts, and prepare reports.

137. What is Boundary Value Analysis?

Answer: A technique where tests are designed to
include boundary values to detect errors at edge
conditions.

138. What is Equivalence Partitioning?

Answer: Dividing input data into valid and invalid
partitions to reduce test cases.

139. What is Load Testing?

Answer: Testing to check system behavior under
expected user loads.

140. What is Stress Testing?

Answer: Testing system performance under extreme or
peak load conditions.
141. What is Configuration Testing?
Answer: Testing how software performs under
different hardware, software, network, and system
configurations.

142. What is the difference between Static

and Dynamic Testing?
Answer: Static testing reviews code and documents
without executing code, while dynamic testing
involves executing the code to validate functionality.

143. What is a Test Harness?

Answer: A set of software and test data configured to
test a program unit by running it under varying
conditions.

144. What is Defect Leakage?

Answer: Defects that were missed during testing but
found by users after release.
145. What is the purpose of a Test Data
Management?
Answer: To ensure appropriate, consistent, and secure
data is available for test execution.

146. What is Compatibility Testing?

Answer: Testing software on different browsers,
devices, operating systems, or networks to ensure
consistent behavior.

147. What is the difference between

Severity and Impact?
Answer: Severity measures how serious a defect is;
impact refers to the effect of the defect on business or
users.

148. What is Monkey Testing?

Answer: Random testing with no specific test cases to
find defects unexpectedly.
149. What is the difference between Alpha
and Beta Testing?
Answer: Alpha testing is done internally by developers
or testers; beta testing is performed by end users in the
real environment.

150. What is a Walkthrough?

Answer: A peer review process where a document or
code is examined informally to find defects.

151. What is the difference between Test

Strategy and Test Plan?
Answer: Test Strategy is a high-level document
outlining the testing approach and objectives across
projects; Test Plan is detailed and specific to a project,
describing what, how, when, and who will perform
testing.

152. What are the different types of

Testing?
Answer: Functional Testing, Non-Functional Testing,
Regression Testing, Smoke Testing, Sanity Testing,
Usability Testing, Performance Testing, Security
Testing, etc.

153. What is the significance of Test Case

Prioritization?
Answer: To focus on testing critical functionalities
first to minimize risk and ensure important features
work properly.

154. What is the difference between

Functional and Regression Testing?
Answer: Functional Testing verifies specific functions
of the software, Regression Testing ensures new
changes don’t adversely affect existing functionality.

155. What is a Bug Life Cycle?

Answer: The process a bug goes through from
detection to closure, including states like New,
Assigned, Open, Fixed, Retested, Reopened, Deferred,
and Closed.
156. What is Test Coverage?
Answer: A metric that measures the extent to which
the software requirements are covered by test cases.

157. What is the role of a Test Analyst?

Answer: To analyze requirements, create test cases,
execute tests, report defects, and ensure the quality of
the product.

158. What is Exploratory Testing?

Answer: Testing without scripts or documentation,
where testers explore the application to discover
defects.

159. What is the difference between Load

Testing and Stress Testing?
Answer: Load Te sting checks system behavior under
expected conditions, Stress Testing evaluates
performance under extreme conditions.
160. What is a Defect Triage Meeting?
Answer: A meeting where defects are reviewed,
prioritized, and assigned for fixing.

161. What is the difference between

Severity and Priority in defect
management?
Answer: Severity refers to the impact of the defect on
the system, while priority indicates how quickly the
defect should be fixed based on business needs.

162. What is the purpose of a Test Summary

Report?
Answer: It provides an overview of testing activities,
results, defect status, and overall quality of the build or
release.

163. What is Regression Testing and when

should it be performed?
Answer: Regression Testing verifies that recent code
changes haven’t affected existing functionality. It
should be performed after bug fixes, enhancements, or
configuration changes.
164. What is the difference between Static
Testing and Dynamic Testing?
Answer: Static testing involves reviewing documents
and code without executing the software; dynamic
testing involves executing the software to verify
functionality.

165. What is a Traceability Matrix?

Answer: A document that maps requirements to their
corresponding test cases to ensure coverage and
completeness.

166. What are the common challenges in

manual testing?
Answer: Time-consuming, repetitive, prone to human
error, difficult to handle large data sets, and limited test
coverage for complex applications.
167. What is Sanity Testing?
Answer: A quick, narrow test to verify specific
functionality or bug fixes before proceeding with more
exhaustive testing.

168. What is Smoke Testing?

Answer: Initial testing to check if the build is stable
enough for detailed testing.

169. What is a Test Case? What does it

include?
Answer: A set of steps with inputs, execution
conditions, and expected results used to validate a
particular function or feature.

170. What is Boundary Value Analysis?

Answer: Testing technique focusing on input values at
the boundaries rather than inside the ranges.
171. What is the difference between Alpha
Testing and Beta Testing?
Answer: Alpha testing is done internally by the QA
team before release; Beta testing is done by actual
users in a real environment after Alpha testing.

172. How do you prioritize test cases?

Answer: Based on risk, business impact, criticality,
and frequency of use of the functionality.

173. What is Ad-hoc Testing?

Answer: Testing without formal planning or
documentation, often used to quickly find defects.

174. What is the purpose of Requirement

Traceability Matrix (RTM)?
Answer: To ensure all requirements are covered by test
cases and tracked throughout the testing process.
175. What is Error Guessing?
Answer: A testing technique where testers use
experience to guess problematic areas and create test
cases accordingly.

176. What is the difference between Test

Plan and Test Strategy?
Answer: Test strategy defines the overall approach;
Test plan details the specific testing activities for a
project.

177. What is the difference between

Functional and Non-Functional Testing?
Answer: Functional tests what the system does; non-
functional tests how the system performs under various
conditions.

178. What is Exploratory Testing?

Answer: Simultaneous learning, test design, and
execution without predefined test cases.
179. What are the phases of the Software
Testing Life Cycle (STLC)?
Answer: Requirement Analysis, Test Planning, Test
Case Development, Environment Setup, Test
Execution, Test Closure.

180. What is Regression Testing?

Answer: Retesting to ensure that changes haven’t
broken existing functionality.

181. What is a Defect Life Cycle?

Answer: The journey of a defect from identification to
closure, including states like New, Assigned, Open,
Fixed, Retested, Reopened, and Closed.

182. What is a Test Scenario?

Answer: A high-level test case that represents a
functionality or a feature to be tested.
183. What is the difference between a Test
Case and a Test Script?
Answer: Test cases are manual testing steps; test
scripts are automated scripts executed by automation
tools.

184. What is a Test Metric?

Answer: A measure used to assess the efficiency and
effectiveness of testing processes (e.g., defect density,
test coverage).

185. How do you handle changing

requirements during testing?
Answer: Update test cases, re-plan testing,
communicate changes with stakeholders, and prioritize
testing based on impact.

186. What is a Defect Priority?

Answer: It indicates the order in which a defect should
be fixed, often classified as High, Medium, or Low.
187. What is a Test Data?
Answer: The input values used to execute test cases.

188. What is a Test Closure Activity?

Answer: Finalizing and archiving test artifacts,
analyzing testing metrics, and preparing closure
reports.

189. What is Integration Testing?

Answer: Testing combined parts of an application to
check if they work together correctly.

190. What is End-to-End Testing?

Answer: Testing the entire application flow from start
to finish in a real-world scenario.

191. What is Black Box Testing?

Answer: Testing without knowledge of the internal
code structure, focusing on input and output.
192. What is White Box Testing?
Answer: Testing based on knowledge of the internal
code and logic.

193. What is a Test Automation Framework?

Answer: A set of guidelines and tools to automate
testing efficiently.

194. What is the difference between

Verification and Validation?
Answer: Verification ensures the product is built right;
Validation ensures the right product is built.

195. What is Usability Testing?

Answer: Testing the user-friendliness and ease of use
of the software.

196. What is the difference between

Severity and Priority?
Answer: Severity is the impact of the defect; Priority
is how soon it should be fixed.
197. What is a Bug Life Cycle?
Answer: The stages a bug goes through from
identification to closure.

198. What is Boundary Value Analysis?

Answer: Testing input values at the boundaries of
input ranges.

199. What is the difference between Sanity

and Smoke Testing?
Answer: Smoke testing checks if the build is stable;
sanity testing verifies specific functionality after
changes.

200. What is Exploratory Testing?

Answer: Simultaneous learning, test design, and
execution without pre-written test cases.
201. What is the difference between Test
Case and Test Scenario?
Answer: Test Scenario is a high-level description of
what to test; Test Case includes detailed steps, inputs,
and expected results.

202. What is Severity in Defect Tracking?

Answer: Severity measures the impact of a defect on
the application's functionality.

203. What is Priority in Defect Tracking?

Answer: Priority determines how quickly a defect
should be fixed based on business needs.

204. What is End-to-End Testing?

Answer: Testing the complete workflow of the
application from start to finish, including integration
with external systems.

205. What is Regression Testing?

Answer: Testing to confirm that recent code changes
have not adversely affected existing features.
206. What is Test Data?
Answer: Data used to execute test cases, including
valid, invalid, and boundary inputs.

207. What is a Bug Report?

Answer: A document detailing the defect, including
steps to reproduce, expected vs actual results, severity,
priority, and screenshots.

208. What is the difference between Load

Testing and Stress Testing?
Answer: Load Testing checks system behavior under
expected load; Stress Testing checks behavior under
extreme or peak loads.

209. What is a Test Plan?

Answer: A document describing the scope, approach,
resources, and schedule of intended test activities.
210. What is the Software Testing Life Cycle
(STLC)?
Answer: Phases include Requirement Analysis, Test
Planning, Test Case Development, Environment Setup,
Test Execution, and Test Closure.