SoftwareTestPilot
42 Q&A · Freshers → Senior

Manual Testing Interview Questions and Answers (2026)

42 real manual testing interview questions and answers spanning freshers to senior QA. Fundamentals, test design (BVA, EP, decision tables), defect management, test types, process metrics, and behavioral scenarios — plus salary bands and 8 People-Also-Ask FAQs.

  • 8 min read
  • Difficulty: Mixed (Easy → Medium)
  • Freshers · 1–5 YOE
  • Updated July 2026
  • Avinash Kamble
Switch to Automation
Avinash Kamble
Founder & QA Engineer at SoftwareTestPilot
Published:
0 / 42 reviewed
0%

1. Manual Testing Fundamentals

Easy Very Common 1 minQ1 / 42

Q1.What is manual testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "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

Manual testing is the process of executing test cases by a human tester without using automation tools — the tester interacts with the application, observes behavior, and reports defects. It is essential for exploratory, usability, ad-hoc, and UAT scenarios where human judgment is irreplaceable.

Tips to remember
  • Open with a one-sentence definition of manual 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 manual testing cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ3
Q2 →
Easy Very Common 1 minQ2 / 42

Q2.What are the advantages of manual testing?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "advantages of 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

Human intuition uncovers UX and visual bugs automation misses; low setup cost for short-lived features; flexible when requirements shift daily; ideal for exploratory and usability testing; and no scripting expertise required.

Tips to remember
  • Open with a one-sentence definition of advantages of manual 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 advantages of manual testing cleanly.
  • Explain setup/teardown ordering and what runs per-test vs per-suite; ordering mistakes are the follow-up question.
RelatedQ4
← Q1Q3 →
Easy Very Common 1 minQ3 / 42

Q3.What are the disadvantages of manual testing?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "disadvantages of 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

Slower and non-repeatable at scale, prone to human error, expensive for regression across releases, hard to run in parallel, and difficult to measure precise performance metrics.

Tips to remember
  • Open with a one-sentence definition of disadvantages of manual 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 disadvantages of manual testing cleanly.
  • Call out test isolation and shared-state risk (data, sessions, ports) before you talk about worker counts.
RelatedQ1Q5
← Q2Q4 →
Easy Very Common 1 minQ4 / 42

Q4.What is the difference between manual testing and automation testing?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "difference between manual testing and automation 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

Manual is human-driven — flexible, exploratory, subjective. Automation is script-driven — fast, repeatable, objective. Manual is best for new features and UX; automation is best for regression, load, and data-driven checks. Modern teams use both.

Tips to remember
  • Open with a one-sentence definition of difference between manual testing and automation 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 difference between manual testing and automation testing cleanly.
RelatedQ2Q6
← Q3Q5 →
Easy Very Common 1 minQ5 / 42

Q5.What skills does a good manual tester need?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

This Manual Testing question checks whether you can go beyond textbook knowledge on What skills does a good manual tester need 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

Domain knowledge, analytical thinking, attention to detail, strong written communication (bug reports), test-design mastery (BVA, EP, decision tables), SQL basics, API testing basics (Postman), and familiarity with Jira, TestRail, or Zephyr.

Tips to remember
  • Anchor the answer in a real Manual Testing project — panels reward specificity on What skills does a good manual tester need over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise What skills does a good manual tester need cleanly.
  • Say how you clean up or roll back the data you touch — DB questions are really data-hygiene questions.
RelatedQ3Q7
← Q4Q6 →
Easy Very Common 1 minQ6 / 42

Q6.What is the difference between QA and QC?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "difference between QA and QC" 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

QA is process-oriented and preventive (audits, reviews, standards, methodology). QC is product-oriented and corrective (inspection, testing, defect detection). QA improves the process; QC verifies the product.

Tips to remember
  • Open with a one-sentence definition of difference between QA and QC, 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 difference between QA and QC cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ4Q8
← Q5Q7 →
Easy Very Common 1 minQ7 / 42

Q7.What is verification vs validation?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "verification vs 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

Verification — are we building the product right? Static, done via reviews and walkthroughs. Validation — are we building the right product? Dynamic, done via test execution and UAT.

Tips to remember
  • Open with a one-sentence definition of verification vs validation, 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 verification vs validation cleanly.
RelatedQ5Q9
← Q6Q8 →
Easy Very Common 1 minQ8 / 42

Q8.What is the difference between a test plan, test strategy, and test case?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "difference between a test plan, test strategy, and test case" 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

Test strategy is a high-level, project-agnostic document (org-wide policy). Test plan is project-specific (scope, schedule, resources, risks). Test case is the lowest level — steps, inputs, expected result for one scenario.

Tips to remember
  • Open with a one-sentence definition of difference between a test plan, test strategy, and test case, 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 difference between a test plan, test strategy, and test case cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ6Q10
← Q7Q9 →
Confidence check

If you can confidently answer the Manual 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 & Test Data Design

Easy Very Common 1 minQ9 / 42

Q9.How do you write a good test case?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Hands-on "how would you write a good test case" 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

A good test case has: unique ID, clear title, precondition, atomic steps, single expected result, traceability to a requirement, priority, and no dependency on other tests. Rule of thumb: another tester should reproduce it exactly from your steps alone.

Tips to remember
  • Walk through write a good test case as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise write a good test case cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ7Q11
← Q8Q10 →
Easy Very Common 1 minQ10 / 42

Q10.What is boundary value analysis (BVA)?

Asked byMicrosoftAccentureInfosysCognizant
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

BVA tests at the edges of input ranges — min, min-1, min+1, max, max-1, max+1. For a text field 5–15 chars: test 4, 5, 6, 14, 15, 16 characters. Bugs cluster at boundaries where developers use wrong operators (< vs ≤).

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.
RelatedQ8Q12
← Q9Q11 →
Easy Very Common 1 minQ11 / 42

Q11.What is equivalence partitioning (EP)?

Asked byCognizantWiproAmazonCapgemini
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

EP divides inputs into partitions where behavior is expected to be identical, then tests one value per partition. For age 18–60: one from <18 (invalid), one from 18–60 (valid), one from >60 (invalid) — three tests instead of dozens.

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.
RelatedQ9Q13
← Q10Q12 →
Easy Very Common 1 minQ12 / 42

Q12.What is decision table testing?

Asked byInfosysCognizantWiproAmazon
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

A decision table lists all combinations of conditions and their expected actions. For a loan-approval rule (age, income, credit score), each row becomes a test case. Guarantees complete logical coverage and exposes missing rules.

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.
RelatedQ10Q14
← Q11Q13 →
Easy Very Common 1 minQ13 / 42

Q13.What is state transition testing?

Asked byAmazonCapgeminiTCSMicrosoft
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

Models the system as states and events. For a login screen: Logged-Out → Logged-In (correct password), Logged-Out → Locked (3 failed attempts). Tests cover valid transitions, invalid transitions, and state boundaries.

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.
RelatedQ11Q15
← Q12Q14 →
Easy Very Common 1 minQ14 / 42

Q14.What is pairwise (orthogonal) testing?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "pairwise (orthogonal) 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

Pairwise testing covers all pairs of input combinations instead of every combination (which explodes combinatorially). Tools like PICT or AllPairs.exe generate the minimum set. Common when you have 5+ parameters with 3+ values each.

Tips to remember
  • Open with a one-sentence definition of pairwise (orthogonal) 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 pairwise (orthogonal) testing cleanly.
RelatedQ12Q16
← Q13Q15 →
Easy Very Common 1 minQ15 / 42

Q15.What is positive vs negative testing?

Asked byTCSMicrosoftAccentureInfosys
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 testing checks the system does what it should with valid inputs (happy path). Negative testing checks the system gracefully handles invalid inputs (letters in a number field, expired token, malformed JSON) without crashing or exposing data.

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.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise positive vs negative testing cleanly.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ13Q17
← Q14Q16 →
Easy Very Common 1 minQ16 / 42

Q16.What is exploratory testing and when do you use it?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "exploratory testing and when do you use it" 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

Exploratory testing is simultaneous learning, test design, and execution — the tester uses charters, heuristics, and domain knowledge to probe the system. Best for new features, incomplete specs, complex workflows, and time-boxed risk assessments. Managed via Session-Based Test Management (SBTM).

Tips to remember
  • Open with a one-sentence definition of exploratory testing and when do you use it, 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 and when do you use it cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ14Q18
← Q15Q17 →
Confidence check

If you can confidently answer the Test Case & Test Data Design 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. Defect Management

Easy Common 1 minQ17 / 42

Q17.Explain the bug life cycle.

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Open-ended "explain bug life cycle" prompts test how you structure a technical answer under pressure. Panels look for a clear opening definition, one worked example, and a closing sentence on the pitfall they were about to ask about next.

Detailed explanation

Standard flow: New → Assigned → Open → In Progress → Fixed → Retest → Verified → Closed. Alternate states: Rejected, Deferred, Duplicate, Not-Reproducible, Reopened. Each transition is logged in Jira for audit and metrics.

Tips to remember
  • Use a 3-part frame for bug life cycle: what it is → how it works → one gotcha you've hit in a real Manual Testing project.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise bug life cycle cleanly.
RelatedQ15Q19
← Q16Q18 →
Easy Common 1 minQ18 / 42

Q18.What is the difference between severity and priority?

Asked byMicrosoftAccentureInfosysCognizant
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

Severity = business impact (Critical/High/Medium/Low). Priority = urgency to fix (P1/P2/P3/P4). A misspelled company name on the homepage is low severity but high priority; a crash on a rarely used feature is high severity but low priority.

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.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between severity and priority cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ16Q20
← Q17Q19 →
Easy Common 1 minQ19 / 42

Q19.What information should a bug report contain?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

This Manual Testing question checks whether you can go beyond textbook knowledge on What information should a bug report contain 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

Title, environment (browser, OS, build, device), preconditions, exact reproduction steps, actual result, expected result, severity, priority, screenshots/screen recording, console + network logs, reproducibility %, and a link to the failing test case.

Tips to remember
  • Anchor the answer in a real Manual Testing project — panels reward specificity on What information should a bug report contain over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise What information should a bug report contain cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ17Q21
← Q18Q20 →
Easy Common 1 minQ20 / 42

Q20.What is defect leakage and how do you measure it?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "defect leakage and how do you measure it" 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

Defect leakage = defects escaped to a later stage (e.g., found in prod that QA missed). Formula: Leaked defects ÷ Total defects × 100. Target < 5%. Track by root cause (missing test, environment gap, unclear requirement) and feed back into test-design.

Tips to remember
  • Open with a one-sentence definition of defect leakage and how do you measure it, 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 and how do you measure it cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ18Q22
← Q19Q21 →
Easy Common 1 minQ21 / 42

Q21.What is defect density?

Asked byAmazonCapgeminiTCSMicrosoft
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

Defect density = number of defects ÷ size of the module (KLOC, function points, or story points). Used to compare module quality and prioritize deeper testing on high-density modules.

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.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ19Q23
← Q20Q22 →
Easy Common 1 minQ22 / 42

Q22.How do you handle a defect the developer rejects as 'Not a bug'?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Hands-on "how would you handle a defect the developer rejects as 'Not 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

Re-verify with the exact steps in a clean environment, capture video + logs, and share back. If disagreement continues, escalate with the requirement/specification reference and the business impact. If the spec is ambiguous, request a three-way call with the PO to lock behavior before closing.

Tips to remember
  • Walk through handle a defect the developer rejects as 'Not a bug' as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise handle a defect the developer rejects as 'Not a bug' cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ20Q24
← Q21Q23 →
Confidence check

If you can confidently answer the Defect 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.

4. Manual Test Types & Levels

Easy Common 1 minQ23 / 42

Q23.What are the levels of testing?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "levels of 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

Four levels: Unit (developers, individual functions), Integration (interactions between modules), System (end-to-end product against requirements), Acceptance (business stakeholders / users). Each level has entry/exit criteria and different owners.

Tips to remember
  • Open with a one-sentence definition of levels of 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 levels of testing cleanly.
RelatedQ21Q25
← Q22Q24 →
Easy Common 1 minQ24 / 42

Q24.What is integration testing and its approaches?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "integration testing and its approaches" 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

Integration testing verifies interactions between modules. Approaches: Big Bang (all at once), Top-Down (stubs replace lower modules), Bottom-Up (drivers replace upper modules), Sandwich (both directions), Incremental (module-by-module).

Tips to remember
  • Open with a one-sentence definition of integration testing and its approaches, 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 integration testing and its approaches cleanly.
  • Say when you'd mock versus hit the real dependency; unconditional mocking is a red flag for integration coverage.
RelatedQ22Q26
← Q23Q25 →
Easy Common 1 minQ25 / 42

Q25.What is smoke vs sanity testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "smoke vs 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 is a shallow, wide check on a new build — do the core flows work at all? Runs before regression. Sanity is a narrow, deep check on a specific area after a small fix. Smoke is done by QA; sanity is often done by devs and QA together.

Tips to remember
  • Open with a one-sentence definition of smoke vs sanity 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 smoke vs sanity testing cleanly.
RelatedQ23Q27
← Q24Q26 →
Easy Common 1 minQ26 / 42

Q26.What is regression testing?

Asked byMicrosoftAccentureInfosysCognizant
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

Regression testing re-runs existing test cases after any code change to confirm nothing that used to work is now broken. Primary automation candidate — grows in size every release. Managed via a curated regression suite plus risk-based prioritization.

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.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ24Q28
← Q25Q27 →
Easy Common 1 minQ27 / 42

Q27.What is retesting?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "retesting" 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

Retesting re-executes the same failed test against a new build after the developer claims to have fixed the bug. Confirms the specific bug is fixed. Complements regression — retesting is bug-specific; regression is broader.

Tips to remember
  • Open with a one-sentence definition of retesting, 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 retesting cleanly.
RelatedQ25Q29
← Q26Q28 →
Easy Common 1 minQ28 / 42

Q28.What is UAT and who performs it?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "UAT and who performs it" 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

User Acceptance Testing is the final validation performed by end users or business stakeholders against real-world scenarios. Two flavors: Alpha (in-house users, controlled) and Beta (external users, limited release).

Tips to remember
  • Open with a one-sentence definition of UAT and who performs it, 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 UAT and who performs it cleanly.
RelatedQ26Q30
← Q27Q29 →
Easy Common 1 minQ29 / 42

Q29.What is compatibility testing?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "compatibility 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

Compatibility testing verifies the application behaves correctly across browsers (Chrome, Safari, Firefox, Edge), OSes (Windows, macOS, iOS, Android), screen resolutions, and network conditions. Runs on BrowserStack, Sauce Labs, or LambdaTest.

Tips to remember
  • Open with a one-sentence definition of compatibility 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 compatibility testing cleanly.
  • Mention capability matrix and cost/queue trade-offs — that's the operational angle panels probe next.
RelatedQ27Q31
← Q28Q30 →
Easy Common 1 minQ30 / 42

Q30.What is accessibility testing?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "accessibility 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

Accessibility testing verifies the application is usable by people with disabilities per WCAG 2.1/2.2 (perceivable, operable, understandable, robust). Tools: axe DevTools, WAVE, Lighthouse. Manual checks with screen readers (NVDA, JAWS, VoiceOver) are irreplaceable.

Tips to remember
  • Open with a one-sentence definition of accessibility 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 accessibility testing cleanly.
RelatedQ28Q32
← Q29Q31 →
Confidence check

If you can confidently answer the Manual Test 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.

5. Test Process, Metrics & Reporting

Easy Common 1 minQ31 / 42

Q31.What is a Requirement Traceability Matrix (RTM)?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "Requirement 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

An RTM maps each requirement to test cases, defects, and business objectives — proves 100% coverage, exposes untested requirements, and simplifies impact analysis when a requirement changes. Usually a spreadsheet or Zephyr/Xray column.

Tips to remember
  • Open with a one-sentence definition of Requirement 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 Requirement Traceability Matrix (RTM) cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ29Q33
← Q30Q32 →
Easy Occasional 1 minQ32 / 42

Q32.What are the common test metrics you track?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "common test metrics you track" 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

Test execution %: executed ÷ planned. Pass %: passed ÷ executed. Defect leakage %: prod defects ÷ total × 100. Defect density, mean time to detect, mean time to repair, automation coverage, and requirements coverage.

Tips to remember
  • Open with a one-sentence definition of common test metrics you track, 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 common test metrics you track cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ30Q34
← Q31Q33 →
Easy Occasional 1 minQ33 / 42

Q33.How do you decide when to stop testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Hands-on "how would you decide when to stop testing" 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

Combine multiple criteria: all planned test cases executed, exit criteria met (e.g., zero P1 open), risk-based coverage complete, defect-arrival rate flattens, and deadline reached with stakeholder sign-off. Never stop on a single metric alone.

Tips to remember
  • Walk through decide when to stop testing as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise decide when to stop testing cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ31Q35
← Q32Q34 →
Easy Occasional 1 minQ34 / 42

Q34.What is Test Closure and what does the report contain?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "Test Closure and what does the report contain" 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

Test Closure formally ends the testing phase. The Test Closure Report contains: summary of executed vs planned, defect statistics by severity/priority, root-cause analysis of leakage, lessons learned, and recommendations for the next release.

Tips to remember
  • Open with a one-sentence definition of Test Closure and what does the report contain, 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 Closure and what does the report contain cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ32Q36
← Q33Q35 →
Easy Occasional 1 minQ35 / 42

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

Risk-based testing prioritizes test effort on features with the highest combined impact × probability of failure. Business-critical flows (payment, login) get exhaustive coverage; low-risk features get sampled. Managed via a risk matrix updated per release.

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 / 42

Q36.What is defect triage?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "defect triage" 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

Defect triage is a recurring meeting (usually daily during a release) where QA, dev leads, and PO review new defects, agree on severity/priority, assign owners, and decide fix-in-release vs defer. Prevents backlog explosion.

Tips to remember
  • Open with a one-sentence definition of defect triage, 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 triage cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ34Q38
← Q35Q37 →
Confidence check

If you can confidently answer the Test Process, Metrics & Reporting 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. Real-World Scenarios & Behavioral

Medium Occasional 1 minQ37 / 42

Q37.How would you test a login page?

Asked byAmazonCapgeminiTCSMicrosoft
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

Positive: valid credentials, remember-me, password reveal. Negative: invalid password, blank fields, SQL injection, XSS in username, expired session, account locked after 3 attempts. Non-functional: response time < 2s, HTTPS, no credentials in URL, no password in local storage, session cookie HttpOnly + Secure, WCAG accessibility, tab navigation, screen-reader labels, mobile responsiveness.

Tips to remember
  • Walk through test a login page as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test a login page cleanly.
  • Reference the specific OWASP category and the check you automate for it, not "we do security testing".
RelatedQ35Q39
← Q36Q38 →
Medium Occasional 1 minQ38 / 42

Q38.How would you test an ATM withdrawal flow?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Hands-on "how would you test an ATM withdrawal 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

Positive: valid card + PIN + amount within balance + within daily limit. Negative: wrong PIN (3 attempts → block), expired card, insufficient balance, exceed daily limit, cash-out of ATM, network drop mid-transaction (rollback), duplicate transaction, currency mismatch. Non-functional: response time, receipt printing, transaction logging, compliance with banking regulations.

Tips to remember
  • Walk through test an ATM withdrawal flow as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test an ATM withdrawal flow cleanly.
RelatedQ36Q40
← Q37Q39 →
Easy Occasional 1 minQ39 / 42

Q39.How would you test a shopping-cart 'Add to Cart' feature?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Hands-on "how would you test a shopping-cart 'Add to Cart' 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

Add single item, add multiple quantities, add out-of-stock item, add to cart from search/wishlist/PDP, cart persistence after logout/login, cart across devices, price updates when discount applied, tax calculation, currency conversion, cart limit (99 items), max cart value, and empty cart edge case.

Tips to remember
  • Walk through test a shopping-cart 'Add to Cart' feature as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test a shopping-cart 'Add to Cart' feature cleanly.
RelatedQ37Q41
← Q38Q40 →
Easy Occasional 1 minQ40 / 42

Q40.What is the toughest bug you have found?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "toughest bug you have found" 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

Structure the answer as STAR: Situation (production issue found in staging), Task (isolate root cause), Action (used browser DevTools + backend logs + DB query to narrow to a race condition in the payment webhook), Result (patched before release, added regression test + monitoring alert). Interviewers score on process, not the bug itself.

Tips to remember
  • Open with a one-sentence definition of toughest bug you have found, 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 toughest bug you have found cleanly.
  • Say how you clean up or roll back the data you touch — DB questions are really data-hygiene questions.
RelatedQ38Q42
← Q39Q41 →
Easy Occasional 1 minQ41 / 42

Q41.How do you handle disagreement with a developer about a bug?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Hands-on "how would you handle disagreement with a developer about 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

Stay factual — share reproduction video, logs, environment, and the requirement or spec. If the requirement is ambiguous, get the PO in a call to lock behavior. Never escalate emotionally; escalate procedurally when specs are missing.

Tips to remember
  • Walk through handle disagreement with a developer about a bug as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise handle disagreement with a developer about a bug cleanly.
RelatedQ39
← Q40Q42 →
Easy Occasional 1 minQ42 / 42

Q42.What would you do if requirements are not clear or missing?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

This Manual Testing question checks whether you can go beyond textbook knowledge on What would you do if requirements are not clear or missing 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

Reach out to the PO/BA in writing, refer to any related user story, competitor product, or industry standard. Write assumptions in the test plan, get sign-off, and log clarifications in a shared doc. Never guess silently — undocumented assumptions cause leakage.

Tips to remember
  • Anchor the answer in a real Manual Testing project — panels reward specificity on What would you do if requirements are not clear or missing over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise What would you do if requirements are not clear or missing cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ40
← Q41
Confidence check

If you can confidently answer the Real-World Scenarios & Behavioral 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 manual testing — Manual testing is the process of executing test cases by a human tester without using automation tools — the tester interacts with the application, observes behavior, and reports d
  2. Q2: What are the advantages of manual testing — Human intuition uncovers UX and visual bugs automation misses; low setup cost for short-lived features; flexible when requirements shift daily; ideal for exploratory and usability
  3. Q3: What are the disadvantages of manual testing — Slower and non-repeatable at scale, prone to human error, expensive for regression across releases, hard to run in parallel, and difficult to measure precise performance metrics.
  4. Q4: What is the difference between manual testing and automation testing — Manual is human-driven — flexible, exploratory, subjective.
  5. Q5: What skills does a good manual tester need — Domain knowledge, analytical thinking, attention to detail, strong written communication (bug reports), test-design mastery (BVA, EP, decision tables), SQL basics, API testing basi

Frequently asked questions

1.What are the top manual testing interview questions and answers?
The 2026 shortlist: SDLC vs STLC, severity vs priority, bug life cycle, boundary value analysis, equivalence partitioning, decision table, smoke vs sanity, regression, retesting, and a real bug report — all covered on this page with 40+ answers.
2.Is manual testing still in demand in 2026?
Yes. Manual QA remains 45% of open QA roles globally in 2026, especially in BFSI, healthcare, insurance, and government. Domain-heavy testing, UAT, exploratory testing, and accessibility auditing cannot be fully automated.
3.What is the salary of a manual tester in India (2026)?
Freshers ₹3.5–5 LPA, 2–4 YOE ₹6–9 LPA, 5+ YOE ₹10–16 LPA. Domain expertise (insurance, banking, healthcare) adds 20–30%. See our Manual Tester Salary guide for city-wise bands.
4.How do I switch from manual to automation testing?
Follow our Manual-to-Automation roadmap: (1) pick Java or Python, (2) learn one tool (Selenium/Playwright), (3) build a POM framework on a real app, (4) add CI/CD, (5) publish on GitHub. Most manual testers transition in 4–6 months of consistent effort.
5.How many test cases should a manual tester write per day?
Industry benchmark is 20–30 well-structured functional test cases per day for a mid-level tester. Complex integration scenarios or compliance tests may drop to 5–10 per day due to research and traceability overhead.
6.What is the difference between retesting and regression testing?
Retesting re-runs the exact failed test after a bug fix to confirm it passes. Regression re-runs a broader suite to confirm the fix didn't break anything else. Retesting is planned per bug; regression is planned per release.
7.What ISTQB certification is best for manual testers?
Start with ISTQB Foundation Level (CTFL). For 3+ YOE, add CTAL-TA (Test Analyst) or CTAL-TM (Test Manager). Domain-specific: ISTQB Mobile Testing, Agile Tester, or Usability Tester.
8.Do manual testers write SQL?
Yes — 80% of manual QA roles in BFSI/enterprise require SQL for back-end validation (select, joins, aggregate, subqueries). See our SQL Interview Questions for QA for the shortlist.

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