SoftwareTestPilot
43 Q&A

Complete Manual Testing Interview Questions & Answers (2026)

Master your QA interview with 70+ manual testing interview questions and answers for 2026. Covers STLC, test cases, bug lifecycle, Agile testing, and more. Start practicing with AI mock interviews.

  • 7 min read
  • Difficulty: Mixed (Easy → Hard)
  • Freshers → Experienced
  • Updated July 17, 2026
  • Avinash Kamble
Start AI mock interview Practice with QA Hub
0 / 43 reviewed
0%

1. Software Testing Fundamentals

Easy Very Common 1 minQ1 / 43

Q1.What is Software Testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "Software Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Software testing is the process of evaluating and verifying that a software application works as expected. It involves executing a system to identify bugs, gaps, or missing requirements.

Example: Checking if a banking app correctly transfers money between accounts while maintaining security and data integrity.

Tips to remember
  • Open with a one-sentence definition of Software Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Software Testing cleanly.
  • Reference the specific OWASP category and the check you automate for it, not "we do security testing".
RelatedQ3
Q2 →
Medium Very Common 1 minQ2 / 43

Q2.What are the Key Principles of Software Testing?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "Key Principles of Software Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: The seven principles defined by ISTQB are:

  1. Testing shows presence of defects — Testing can prove defects exist but cannot prove they don't.
  2. Exhaustive testing is impossible — You cannot test everything; use risk-based prioritization.
  3. Early testing saves time & money — Shift-left testing reduces costs.
  4. Defects cluster together — Most bugs are found in a small number of modules (Pareto 80/20 rule).
  5. Pesticide paradox — Repeating the same tests finds no new bugs; review and update regularly.
  6. Testing is context-dependent — E-commerce testing differs from healthcare app testing.
  7. Absence-of-errors fallacy — A bug-free app that doesn't meet user needs is useless.
Tips to remember
  • Open with a one-sentence definition of Key Principles of Software Testing, then a concrete Manual Testing example — never start with history or theory.
  • Group the Key Principles of Software Testing points into 2–3 buckets so you can recall them under pressure without missing one.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ4
← Q1Q3 →
Easy Very Common 1 minQ3 / 43

Q3.What is the Difference Between Verification and Validation?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "Difference Between Verification and Validation" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation
VerificationValidation
Are we building the product right?Are we building the right product?
Reviews, walkthroughs, inspectionsTesting the actual application
Static testing (no code execution)Dynamic testing (code execution)
Done before validationDone after verification
Tips to remember
  • Open with a one-sentence definition of Difference Between Verification and Validation, then a concrete Manual Testing example — never start with history or theory.
  • Rebuild the Difference Between Verification and Validation comparison table from memory before the interview — panels probe the least-used row.
RelatedQ1Q5
← Q2Q4 →
Easy Very Common 1 minQ4 / 43

Q4.What is SDLC? Explain Phases.

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "SDLC? Explain Phases" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: SDLC (Software Development Life Cycle) includes: Requirement Gathering → Analysis → Design → Development → Testing → Deployment → Maintenance.

Tips to remember
  • Open with a one-sentence definition of SDLC? Explain Phases, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise SDLC? Explain Phases cleanly.
RelatedQ2Q6
← Q3Q5 →
Easy Very Common 1 minQ5 / 43

Q5.What is STLC? Explain Phases.

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "STLC? Explain Phases" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: STLC (Software Testing Life Cycle) includes: Requirement Analysis → Test Planning → Test Case Development → Environment Setup → Test Execution → Bug Reporting → Test Closure.

Practice these concepts with our AI Mock Interview.

Tips to remember
  • Open with a one-sentence definition of STLC? Explain Phases, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise STLC? Explain Phases cleanly.
  • Say when you'd mock versus hit the real dependency; unconditional mocking is a red flag for integration coverage.
RelatedQ3Q7
← Q4Q6 →
Confidence check

If you can confidently answer the Software Testing Fundamentals questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

2. Test Case Design Techniques

Easy Very Common 1 minQ6 / 43

Q6.What is a Test Case? What Are the Essential Components?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "Test Case? What Are the Essential Components" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: A test case is a set of conditions used to verify a specific functionality.

Essential components:

  • Test Case ID
  • Test Title / Description
  • Preconditions
  • Test Steps
  • Test Data
  • Expected Result
  • Actual Result
  • Status (Pass/Fail)
Tips to remember
  • Open with a one-sentence definition of Test Case? What Are the Essential Components, then a concrete Manual Testing example — never start with history or theory.
  • Group the Test Case? What Are the Essential Components points into 2–3 buckets so you can recall them under pressure without missing one.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ4Q8
← Q5Q7 →
Easy Very Common 1 minQ7 / 43

Q7.What is Boundary Value Analysis (BVA)?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "Boundary Value Analysis (BVA)" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: BVA tests values at the edges of equivalence partitions.

Example: For a field accepting values 1–100: test 0 (invalid lower), 1 (valid lower), 2 (just above), 99 (just below upper), 100 (valid upper), 101 (invalid upper).

Tips to remember
  • Open with a one-sentence definition of Boundary Value Analysis (BVA), then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Boundary Value Analysis (BVA) cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ5Q9
← Q6Q8 →
Easy Very Common 1 minQ8 / 43

Q8.What is Equivalence Partitioning (EP)?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "Equivalence Partitioning (EP)" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: EP divides input data into valid and invalid partitions. Testing one value from each partition is sufficient.

Example: For an age field 18–60: valid partition 18–60 (test 30); invalid <18 (test 15); invalid >60 (test 65).

Tips to remember
  • Open with a one-sentence definition of Equivalence Partitioning (EP), then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Equivalence Partitioning (EP) cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ6Q10
← Q7Q9 →
Easy Very Common 1 minQ9 / 43

Q9.What is Decision Table Testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "Decision Table Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Decision tables capture business logic with combinations of conditions and their corresponding actions. Example: Login page: Username (Valid/Invalid) × Password (Valid/Invalid) × Captcha (Correct/Wrong) → 8 test combinations.

Tips to remember
  • Open with a one-sentence definition of Decision Table Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Decision Table Testing cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ7Q11
← Q8Q10 →
Easy Very Common 1 minQ10 / 43

Q10.What is State Transition Testing?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "State Transition Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: State transition testing verifies system behavior as it moves through different states. Example: ATM workflow: Idle → Card Inserted → PIN Entered → Menu → Transaction → Eject Card → Idle.

Tips to remember
  • Open with a one-sentence definition of State Transition Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise State Transition Testing cleanly.
RelatedQ8Q12
← Q9Q11 →
Confidence check

If you can confidently answer the Test Case Design Techniques questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

3. Testing Types & Levels

Easy Very Common 1 minQ11 / 43

Q11.What is the Difference Between Smoke and Sanity Testing?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "Difference Between Smoke and Sanity Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation
Smoke TestingSanity Testing
Tests major/critical functionalitiesTests specific functionality after changes
Done on every buildDone on stable builds after minor fixes
Shallow and broadDeep and narrow
Gatekeeper for further testingQuick check for bug fixes
Tips to remember
  • Open with a one-sentence definition of Difference Between Smoke and Sanity Testing, then a concrete Manual Testing example — never start with history or theory.
  • Rebuild the Difference Between Smoke and Sanity Testing comparison table from memory before the interview — panels probe the least-used row.
RelatedQ9Q13
← Q10Q12 →
Easy Very Common 1 minQ12 / 43

Q12.What is Regression Testing?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "Regression Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Regression testing ensures new code changes don't break existing functionality. Learn how this works in practice in our Selenium interview questions guide.

Tips to remember
  • Open with a one-sentence definition of Regression Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Regression Testing cleanly.
RelatedQ10Q14
← Q11Q13 →
Easy Very Common 1 minQ13 / 43

Q13.What is Exploratory Testing?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "Exploratory Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Simultaneous learning, test design, and execution without predefined test cases. Testers explore the application freely to find unexpected bugs.

Tips to remember
  • Open with a one-sentence definition of Exploratory Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Exploratory Testing cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ11Q15
← Q12Q14 →
Easy Very Common 1 minQ14 / 43

Q14.What is Ad-hoc Testing?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "Ad-hoc Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Informal testing without planning or documentation. Done randomly to find defects missed by structured testing.

Tips to remember
  • Open with a one-sentence definition of Ad-hoc Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Ad-hoc Testing cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ12Q16
← Q13Q15 →
Easy Very Common 1 minQ15 / 43

Q15.What is Monkey Testing?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "Monkey Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Testing with random inputs and actions to see how the system behaves under unexpected conditions. No test cases, no expected results.

Tips to remember
  • Open with a one-sentence definition of Monkey Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Monkey Testing cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ13Q17
← Q14Q16 →
Easy Very Common 1 minQ16 / 43

Q16.What is Positive vs Negative Testing?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "Positive vs Negative Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation
Positive TestingNegative Testing
Tests valid inputsTests invalid inputs
Verifies expected behaviorVerifies error handling
"System accepts correct login""System rejects wrong password"
Tips to remember
  • Open with a one-sentence definition of Positive vs Negative Testing, then a concrete Manual Testing example — never start with history or theory.
  • Rebuild the Positive vs Negative Testing comparison table from memory before the interview — panels probe the least-used row.
RelatedQ14Q18
← Q15Q17 →
Easy Very Common 1 minQ17 / 43

Q17.What is Static vs Dynamic Testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "Static vs Dynamic Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation
Static TestingDynamic Testing
No code executionCode execution required
Reviews, walkthroughs, inspectionsFunctional, regression, performance testing
Finds defects earlyFinds runtime issues
Tips to remember
  • Open with a one-sentence definition of Static vs Dynamic Testing, then a concrete Manual Testing example — never start with history or theory.
  • Rebuild the Static vs Dynamic Testing comparison table from memory before the interview — panels probe the least-used row.
  • Use percentiles (P90/P95) and a concrete SLA rather than averages — averages hide the failures interviewers care about.
RelatedQ15Q19
← Q16Q18 →
Easy Common 1 minQ18 / 43

Q18.What is White Box, Black Box, and Gray Box Testing?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "White Box, Black Box, and Gray Box Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation
  • White Box: Tests internal code structure (unit testing, code coverage).
  • Black Box: Tests functionality without knowing internal code (UI testing, API testing).
  • Gray Box: Combination — knows partial internal structure (integration testing).
Tips to remember
  • Open with a one-sentence definition of White Box, Black Box, and Gray Box Testing, then a concrete Manual Testing example — never start with history or theory.
  • Group the White Box, Black Box, and Gray Box Testing points into 2–3 buckets so you can recall them under pressure without missing one.
RelatedQ16Q20
← Q17Q19 →
Confidence check

If you can confidently answer the Testing Types & Levels questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

4. Bug Reporting & Management

Easy Common 1 minQ19 / 43

Q19.What is a Bug Life Cycle?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "Bug Life Cycle" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: New → Assigned → Open → Fixed → Retest → Closed | Reopened → Deferred → Rejected.

Tips to remember
  • Open with a one-sentence definition of Bug Life Cycle, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Bug Life Cycle cleanly.
RelatedQ17Q21
← Q18Q20 →
Easy Common 1 minQ20 / 43

Q20.What is the Difference Between Severity and Priority?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "Difference Between Severity and Priority" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation
SeverityPriority
How severe is the bug's impact?How urgently should it be fixed?
High: App crashes on loginHigh: Business-critical flow broken
Low: Minor UI misalignmentLow: Cosmetic issue, can wait
Tips to remember
  • Open with a one-sentence definition of Difference Between Severity and Priority, then a concrete Manual Testing example — never start with history or theory.
  • Rebuild the Difference Between Severity and Priority comparison table from memory before the interview — panels probe the least-used row.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ18Q22
← Q19Q21 →
Easy Common 1 minQ21 / 43

Q21.What Makes a Good Bug Report?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

This Manual Testing question checks whether you can go beyond textbook knowledge on What Makes a Good Bug Report and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation
  • Clear and descriptive title
  • Steps to reproduce
  • Actual vs expected result
  • Screenshots / video (if applicable)
  • Environment details (OS, browser, device)
  • Severity & Priority
  • Test data used
Tips to remember
  • Anchor the answer in a real Manual Testing project — panels reward specificity on What Makes a Good Bug Report over textbook wording.
  • Group the What Makes a Good Bug Report points into 2–3 buckets so you can recall them under pressure without missing one.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ19Q23
← Q20Q22 →
Easy Common 1 minQ22 / 43

Q22.What is Defect Leakage?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "Defect Leakage" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: When bugs are missed during testing and found by end users in production.

Tips to remember
  • Open with a one-sentence definition of Defect Leakage, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Defect Leakage cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ20Q24
← Q21Q23 →
Easy Common 1 minQ23 / 43

Q23.What is Defect Density?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "Defect Density" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Number of defects per size of the software module (e.g., defects per KLOC).

Tips to remember
  • Open with a one-sentence definition of Defect Density, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Defect Density cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ21Q25
← Q22Q24 →
Confidence check

If you can confidently answer the Bug Reporting & Management questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

5. Agile & Scrum Testing

Easy Common 1 minQ24 / 43

Q24.What is Agile Testing?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "Agile Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Testing integrated throughout development in short iterations (sprints), with continuous feedback and collaboration.

Tips to remember
  • Open with a one-sentence definition of Agile Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Agile Testing cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ22Q26
← Q23Q25 →
Easy Common 1 minQ25 / 43

Q25.What is a Test Plan in Agile?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "Test Plan in Agile" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: In Agile, testing is planned per sprint rather than upfront. Test plans are lightweight and evolve continuously.

Tips to remember
  • Open with a one-sentence definition of Test Plan in Agile, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Test Plan in Agile cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ23Q27
← Q24Q26 →
Easy Common 1 minQ26 / 43

Q26.What is the Role of a QA in Daily Standups?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "Role of a QA in Daily Standups" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Share testing progress, blockers, and risks. Highlight bug trends and quality metrics.

Tips to remember
  • Open with a one-sentence definition of Role of a QA in Daily Standups, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Role of a QA in Daily Standups cleanly.
RelatedQ24Q28
← Q25Q27 →
Easy Common 1 minQ27 / 43

Q27.What is Definition of Done (DoD)?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "Definition of Done (DoD)" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Criteria a user story must meet to be considered complete — including testing, code review, documentation, and acceptance criteria.

Tips to remember
  • Open with a one-sentence definition of Definition of Done (DoD), then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Definition of Done (DoD) cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ25Q29
← Q26Q28 →
Easy Common 1 minQ28 / 43

Q28.What is Shift-Left Testing?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "Shift-Left Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Moving testing earlier in the SDLC. Testers participate in requirement analysis and design reviews before development begins.

Tips to remember
  • Open with a one-sentence definition of Shift-Left Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Shift-Left Testing cleanly.
RelatedQ26Q30
← Q27Q29 →
Easy Common 1 minQ29 / 43

Q29.What is Test-Driven Development (TDD)?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "Test-Driven Development (TDD)" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Write failing tests first, then write code to pass them. Ensures code is testable and covers requirements.

Tips to remember
  • Open with a one-sentence definition of Test-Driven Development (TDD), then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Test-Driven Development (TDD) cleanly.
RelatedQ27Q31
← Q28Q30 →
Easy Common 1 minQ30 / 43

Q30.What is Behavior-Driven Development (BDD)?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "Behavior-Driven Development (BDD)" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Extension of TDD using natural language (Gherkin format: Given–When–Then) to define behaviors. Tools: Cucumber, SpecFlow.

Tips to remember
  • Open with a one-sentence definition of Behavior-Driven Development (BDD), then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Behavior-Driven Development (BDD) cleanly.
RelatedQ28Q32
← Q29Q31 →
Confidence check

If you can confidently answer the Agile & Scrum Testing questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

6. Test Management & Metrics

Easy Common 1 minQ31 / 43

Q31.What is a Traceability Matrix (RTM)?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "Traceability Matrix (RTM)" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: A document mapping requirements to test cases, ensuring every requirement has a corresponding test.

Tips to remember
  • Open with a one-sentence definition of Traceability Matrix (RTM), then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Traceability Matrix (RTM) cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ29Q33
← Q30Q32 →
Easy Common 1 minQ32 / 43

Q32.What are Common Test Metrics?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "Common Test Metrics" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation
MetricPurpose
Test Coverage %What percentage of requirements are tested
Defect DensityBugs per module size
Test Execution %How many planned tests executed
Pass/Fail RateTest success percentage
Defect Leakage %Bugs found in production
Tips to remember
  • Open with a one-sentence definition of Common Test Metrics, then a concrete Manual Testing example — never start with history or theory.
  • Rebuild the Common Test Metrics comparison table from memory before the interview — panels probe the least-used row.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ30Q34
← Q31Q33 →
Easy Occasional 1 minQ33 / 43

Q33.What is Test Coverage?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "Test Coverage" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: A measure of how much of the application has been tested — includes requirements coverage, code coverage, and risk coverage.

Tips to remember
  • Open with a one-sentence definition of Test Coverage, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Test Coverage cleanly.
RelatedQ31Q35
← Q32Q34 →
Easy Occasional 1 minQ34 / 43

Q34.What is a Test Summary Report?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "Test Summary Report" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: A document prepared at test closure summarizing: what was tested, results, defects found, metrics, and recommendations.

Tips to remember
  • Open with a one-sentence definition of Test Summary Report, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Test Summary Report cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ32Q36
← Q33Q35 →
Confidence check

If you can confidently answer the Test Management & Metrics questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

7. QA Best Practices

Easy Occasional 1 minQ35 / 43

Q35.What is Risk-Based Testing?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "Risk-Based Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Answer: Prioritizing testing based on the risk (probability × impact) of failure.

Tips to remember
  • Open with a one-sentence definition of Risk-Based Testing, then a concrete Manual Testing example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Risk-Based Testing cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ33Q37
← Q34Q36 →
Easy Occasional 1 minQ36 / 43

Q36.How Do You Prioritize Test Cases?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Hands-on "how would you Prioritize Test Cases" questions reveal whether you've actually shipped Manual Testing code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
  • Critical business functionality
  • High-risk / high-impact areas
  • Frequently used features
  • Recently changed code
  • Customer-reported issues
Tips to remember
  • Walk through Prioritize Test Cases as numbered steps and call out the tool, command, or API used at each step.
  • Group the Prioritize Test Cases points into 2–3 buckets so you can recall them under pressure without missing one.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ34Q38
← Q35Q37 →
Easy Occasional 1 minQ37 / 43

Q37.What Are Common Mistakes in Manual Testing?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "Common Mistakes in Manual Testing" to confirm you can define the concept in one crisp line before going deeper. In Manual Testing rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation
  1. Testing without understanding requirements
  2. Skipping negative test scenarios
  3. Not updating test cases
  4. Poor bug report quality
  5. Ignoring exploratory testing
Tips to remember
  • Open with a one-sentence definition of Common Mistakes in Manual Testing, then a concrete Manual Testing example — never start with history or theory.
  • Group the Common Mistakes in Manual Testing points into 2–3 buckets so you can recall them under pressure without missing one.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ35Q39
← Q36Q38 →
Easy Occasional 1 minQ38 / 43

Q38.What's the Difference Between Test Strategy and Test Plan?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Comparison questions like this test whether you understand Test Strategy vs Test Plan at a design level — not just that both exist, but when to pick one over the other. Panels use it to see if you can defend a trade-off with a real project example.

Detailed explanation
Test StrategyTest Plan
High-level documentDetailed execution document
Created by Test ManagerCreated by Test Lead
Defines "what" and "why"Defines "how" and "when"
Applies to entire projectApplies to specific project/release
Tips to remember
  • Structure the answer as a small table in your head: dimension, option A, option B — and close with "I'd pick X when Y".
  • Rebuild the Test Strategy vs Test Plan comparison table from memory before the interview — panels probe the least-used row.
RelatedQ36Q40
← Q37Q39 →
Confidence check

If you can confidently answer the QA Best Practices questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

8. Real-World Scenario Questions

Easy Occasional 1 minQ39 / 43

Q39.How Would You Test a Login Page?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Hands-on "how would you Test a Login Page" questions reveal whether you've actually shipped Manual Testing code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
  1. Positive: Valid username + password → success.
  2. Negative: Invalid username, wrong password, empty fields.
  3. Boundary: Max/min password length.
  4. Security: SQL injection, brute force, session timeout.
  5. UX: Remember me, forgot password, password visibility toggle.
  6. Cross-browser: Chrome, Firefox, Safari, Edge.
Tips to remember
  • Walk through Test a Login Page as numbered steps and call out the tool, command, or API used at each step.
  • Group the Test a Login Page points into 2–3 buckets so you can recall them under pressure without missing one.
  • Reference the specific OWASP category and the check you automate for it, not "we do security testing".
RelatedQ37Q41
← Q38Q40 →
Easy Occasional 1 minQ40 / 43

Q40.How Would You Test an E-commerce Checkout Flow?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Hands-on "how would you Test an E-commerce Checkout Flow" questions reveal whether you've actually shipped Manual Testing code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
  1. Add items to cart → update quantity → remove items.
  2. Apply coupon → verify discount.
  3. Enter shipping address → validate fields.
  4. Select payment method → complete payment.
  5. Verify order confirmation email.
  6. Edge cases: empty cart, expired coupon, payment failure, network timeout.
Tips to remember
  • Walk through Test an E-commerce Checkout Flow as numbered steps and call out the tool, command, or API used at each step.
  • Group the Test an E-commerce Checkout Flow points into 2–3 buckets so you can recall them under pressure without missing one.
RelatedQ38Q42
← Q39Q41 →
Medium Occasional 1 minQ41 / 43

Q41.How Would You Test a File Upload Feature?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Hands-on "how would you Test a File Upload Feature" questions reveal whether you've actually shipped Manual Testing code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
  • File type validation (PDF, JPG, PNG)
  • File size limits (test boundaries)
  • Multiple file upload
  • Special characters in filenames
  • Upload progress indicator
  • Cancel upload mid-way
  • Network interruption during upload

You can extend any of these scenarios into automation later — see our Playwright interview questions and API testing interview questions for the next step.

Tips to remember
  • Walk through Test a File Upload Feature as numbered steps and call out the tool, command, or API used at each step.
  • Group the Test a File Upload Feature points into 2–3 buckets so you can recall them under pressure without missing one.
RelatedQ39Q43
← Q40Q42 →
Easy Occasional 1 minQ42 / 43

Q42.How Do You Handle a Situation Where Developers Reject a Bug?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Hands-on "how would you Handle a Situation Where Developers Reject a Bug" questions reveal whether you've actually shipped Manual Testing code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation
  1. Re-review the bug to confirm it's valid.
  2. Provide clear evidence (steps, screenshots, logs).
  3. Explain the business impact.
  4. Escalate with the product manager if needed.
  5. Document the discussion for future reference.
Tips to remember
  • Walk through Handle a Situation Where Developers Reject a Bug as numbered steps and call out the tool, command, or API used at each step.
  • Group the Handle a Situation Where Developers Reject a Bug points into 2–3 buckets so you can recall them under pressure without missing one.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ40
← Q41Q43 →
Easy Occasional 1 minQ43 / 43

Q43.What's Your Approach to Testing When Requirements Are Unclear?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

This Manual Testing question checks whether you can go beyond textbook knowledge on What's Your Approach to Testing When Requirements Are Unclear and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation
  1. Ask clarifying questions to stakeholders.
  2. Document assumptions.
  3. Use exploratory testing to discover behavior.
  4. Update test cases as requirements evolve.
  5. Collaborate in refinement sessions.
Tips to remember
  • Anchor the answer in a real Manual Testing project — panels reward specificity on What's Your Approach to Testing When Requirements Are Unclear over textbook wording.
  • Group the What's Your Approach to Testing When Requirements Are Unclear points into 2–3 buckets so you can recall them under pressure without missing one.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ41
← Q42
Confidence check

If you can confidently answer the Real-World Scenario Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

Quick revision

  1. Q1: What is Software Testing — Answer: Software testing is the process of evaluating and verifying that a software application works as expected.
  2. Q2: What are the Key Principles of Software Testing — Answer: The seven principles defined by ISTQB are: Testing shows presence of defects — Testing can prove defects exist but cannot prove they don't.
  3. Q3: What is the Difference Between Verification and Validation — Verification Validation Are we building the product right?
  4. Q4: What is SDLC? Explain Phases. — Answer: SDLC (Software Development Life Cycle) includes: Requirement Gathering → Analysis → Design → Development → Testing → Deployment → Maintenance.
  5. Q5: What is STLC? Explain Phases. — Answer: STLC (Software Testing Life Cycle) includes: Requirement Analysis → Test Planning → Test Case Development → Environment Setup → Test Execution → Bug Reporting → Test Closur

Frequently asked questions

1.How many manual testing interview questions does this guide cover?
70+ questions and answers spanning fundamentals, test design, testing types, bug reporting, Agile/Scrum, metrics, best practices and real-world scenarios — aligned to what hiring managers actually ask in 2026.
2.Is this guide suitable for freshers?
Yes. Freshers can start from Section 1 (fundamentals) and Section 2 (test case design). Experienced testers can jump to Sections 5–8 for Agile, metrics, best practices and scenario questions.
3.What is the difference between severity and priority?
Severity describes the technical impact of a bug (how badly it breaks the system), while priority describes how urgently the business wants it fixed. A typo on a homepage may be low severity but high priority before a launch.
4.What is STLC?
Software Testing Life Cycle: Requirement Analysis → Test Planning → Test Case Development → Environment Setup → Test Execution → Bug Reporting → Test Closure.
5.How do I practice these manual testing questions out loud?
Use our free AI Mock Interview at /ai-mock-interview. It asks manual testing questions in voice, scores your answers in real time and gives personalized feedback so you walk into the real interview confident.
6.Will manual testing still be relevant in 2026?
Yes. Manual testing is essential for exploratory testing, accessibility, UX validation and domain-heavy products. Even highly automated teams rely on strong manual fundamentals for test design and bug triage.

Was this article helpful?

Cluster · QA Career

More from QA Interview Questions

Behavioral, framework, coding — full interview prep.

Pillar guide · 11 articles
More in this cluster
From the QA Career pillar
Topic mapConcepts · Tools · People · Standards

Related concepts, tools & standards around Manual Testing

A quick reference of the people, companies, frameworks and technologies most often mentioned alongside Manual Testing in real QA teams — useful when you're mapping a learning path, preparing for interviews, or scoping a new project.

Core testing concepts
Test PyramidShift-Left TestingBehavior-Driven DevelopmentTest-Driven DevelopmentPage Object ModelContract TestingExploratory TestingRisk-Based TestingEquivalence PartitioningBoundary Value Analysis
Testing tools
SeleniumPlaywrightCypressAppiumJMeterPostmanTestRailBrowserStack
Programming languages
JavaPythonJavaScriptTypeScriptC#SQL
Test frameworks
TestNGJUnit 5pytestCucumber (BDD)REST AssuredRobot Framework
Automation tools
WebDriverIOPuppeteerKarate DSLDetox (React Native)Nightwatch.js
API testing tools
PostmanInsomniaREST AssuredSwagger / OpenAPIPact (Contract Testing)Newman CLI
DevOps & CI/CD
JenkinsGitHub ActionsGitLab CI/CDCircleCIDockerKubernetes
Cloud & device platforms
AWSGoogle CloudMicrosoft AzureSauce LabsLambdaTest
Certifications worth knowing
ISTQB Foundation LevelISTQB Advanced — Test AnalystISTQB Agile TesterCertified Selenium ProfessionalAWS Certified DevOps EngineerCertified ScrumMaster (CSM)
Related interview topics
Selenium Interview Q&APlaywright Interview Q&AAPI Testing Interview Q&ASQL Interview Q&ASDET Interview Q&AManual Testing Interview Q&A
Thought leaders to follow
Kent BeckLisa CrispinJanet GregoryJames BachMichael BoltonAngie Jones
Companies hiring for this skill
GoogleMicrosoftAmazonMetaNetflixAtlassianThoughtWorksInfosysTCSWipro

Key takeaways

  • Master the fundamentals before tackling advanced Manual Testing scenarios.
  • Always explain trade-offs — interviewers reward judgement, not memorisation.
  • Use real project examples; generic answers blend in.
  • Practice answers out loud — written prep doesn't transfer to live rounds.
  • Revise the 30-second cheat sheet the night before your interview.
  • Keep one strong scenario story ready for every section above.
Start a free AI mock interview
Run a live QA mock interview tailored to this topic and get per-skill scoring in minutes.
Read Start a free AI mock interview
ATS Resume Review
Free resume scan tuned for QA roles.
Read ATS Resume Review
QA Practice Hub
Hands-on labs for test design and automation.
Read QA Practice Hub
QA Jobs Radar
Fresh SDET & QA roles, updated daily.
Read QA Jobs Radar

Manual Testing jobs hiring now

Live, indexable Manual Testing openings — updated daily in Jobs Radar.

Browse all QA jobs on Jobs Radar

Loading current openings…

Home

Discussion

Ask a question, share your experience, or correct us. Be kind — real people are reading.

?
Sign in to join the discussion →