Manual Testing Interview Questions (2026)

Manual testing is human-led checking of software behavior using requirements, observation, and judgment.

It is strongest for new features, usability issues, exploratory work, and cases where human interpretation matters.

manual testing changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

A good test case has a purpose, preconditions, test data, steps, expected result, priority, and traceability to a requirement.

It should be clear enough for another tester to run without guessing.

test case changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

A scenario is a high-level condition to test; a test case is the detailed set of steps and expected results.

For login, 'invalid password' is a scenario; entering a specific email and password is a case.

Severity is the technical or user impact of a defect. Priority is how soon it should be fixed.

A crash in a rare admin path can be high severity and lower priority. A typo on the home page logo can be low severity and high priority.

The defect life cycle is the path a bug follows from discovery to closure.

Typical states include new, assigned, open, fixed, retest, reopened, deferred, rejected, and closed.

defect life cycle changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Smoke testing is a quick check that the build's critical paths work before deeper testing starts.

It answers: is this build stable enough to test?

smoke testing changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Sanity testing is a focused check after a specific change or fix.

Smoke is broad and shallow. Sanity is narrow and targeted.

sanity testing changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Regression testing checks that existing working behavior still works after a change.

It matters because fixes and new features often break nearby flows.

regression testing changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Retesting checks whether a specific defect is fixed. Regression checks whether the fix broke other behavior.

Both are often needed before closing a defect.

retesting changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Boundary value analysis tests values at the edge of valid and invalid ranges.

Defects often appear at limits such as 0, 1, max, and max plus 1.

boundary value analysis changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Equivalence partitioning groups inputs that should behave the same, then tests one or a few representatives.

It reduces test count without losing meaningful coverage.

equivalence partitioning changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Exploratory testing is disciplined when it uses a charter, time box, notes, and evidence.

It is not random clicking. It is learning and testing at the same time.

exploratory testing changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Test data decides which branches, permissions, limits, and failures you can observe.

A good tester prepares valid, invalid, boundary, duplicate, expired, and permission-based data.

test data changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Traceability connects requirements, test cases, execution results, and defects.

It helps show what was covered and what remains risky.

traceability changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Exit criteria are agreed conditions for stopping a test phase.

Examples include critical cases passed, no open blocker defects, known risks accepted, and test evidence reviewed.

exit criteria changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Cover valid login, invalid password, unknown user, locked account, empty fields, password masking, remember me, session timeout, rate limit, and recovery links.

Mention security and usability cases after core functional checks.

writing login test cases changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Test allowed type, blocked type, size limit, empty file, duplicate file, cancel, network failure, progress, preview, delete, and virus-scan message if present.

Use real files with known size and extension.

testing file upload changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Check exact match, partial match, no result, case sensitivity, special characters, leading spaces, sort order, filters, pagination, and response time.

Search often fails around empty and special inputs.

testing search changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Cover cart totals, discounts, tax, shipping, address validation, payment success, payment failure, retry, duplicate submit, receipt, and order history.

Payment flows need test cards and clear rollback rules.

testing checkout changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Include title, environment, build, steps, expected result, actual result, test data, evidence, severity, priority, and reproducibility.

A clear report lowers back-and-forth.

reporting a bug changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Group defects by impact, reproducibility, affected users, business date, workaround, and dependency.

Triage is a team decision, not just a QA label.

triaging defects changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Use the original reproduction steps, the same data when possible, then test nearby paths that could be affected by the fix.

Attach evidence before closing.

retesting a fixed bug changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Pick critical user journeys, changed modules, integrations, high-defect areas, and cases tied to business risk.

Regression should be risk-based, not just the whole suite every time.

running regression changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Write a charter, time box the session, note coverage, capture defects, and summarize findings.

The session output should be reviewable.

exploratory charter changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Create users for each role, verify allowed actions, blocked actions, direct URL access, API side effects if visible, and audit logs.

Permission bugs often appear outside the main UI path.

testing permissions changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Check translated labels, date and number formats, text overflow, sorting, currency, directionality if needed, and fallback language.

Use real content, not only short sample strings.

testing localization changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Check viewport, touch targets, keyboard behavior, orientation, network changes, scrolling, forms, and device-specific browser issues.

Use actual devices for final checks when risk is high.

testing mobile web changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

State scope, build, cases run, pass and fail count, blocked items, open defects, risk, recommendation, and evidence links.

Executives need risk, not raw case lists.

test summary report changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Ask for examples, acceptance criteria, edge cases, and expected behavior before treating your assumption as truth.

Log assumptions if testing must start before answers arrive.

requirement ambiguity changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Use open defect severity, failed critical paths, business impact, workaround quality, test coverage, and accepted risks.

QA provides evidence. Release ownership is shared.

release recommendation changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Reproduce it, confirm card type and gateway response, check workaround, assign high severity, and escalate with evidence.

Business impact decides priority.

payment blocker changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Recheck environment, data, steps, logs, timing, browser, and user role, then narrow the case and add evidence.

Don't argue from memory. Bring data.

unreproducible bug changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Identify impacted flows, update priority cases, run focused regression, and document untested risk.

Time-boxed risk testing beats pretending full coverage happened.

late requirement change changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Log it as blocked, request data or access, test alternate coverage if possible, and call out release risk.

Blocked is not passed.

blocked test case changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Cluster them by area, user impact, and business deadline, then separate blockers from polish items.

A clean summary gets decisions faster.

too many defects changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Compare steps, environment, actual result, root area, and affected version before marking it duplicate.

A similar symptom may still have a different cause.

duplicate defect changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Compare config, data volume, permissions, third-party services, logs, and release version.

Production bugs often come from environment differences.

production-only bug changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Ask for expected behavior, write assumptions, use comparable flows, and focus on user value and obvious risk.

Don't invent rules silently.

feature without acceptance criteria changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Explain user impact, frequency, data loss, security, and workaround, then let triage decide.

Severity should be evidence-based.

developer rejects severity changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Run smoke paths, changed-area tests, integration touchpoints, and the top business flows.

Uncovered areas must be explicit.

fast regression ask changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

It is too vague.

A better title says condition and failure, such as 'Locked user can still reach dashboard after password reset'.

bad bug title changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Check case coverage, data, environment, assumptions, and whether the expected result matched real user need.

Passing a weak case doesn't prove the product works.

false pass changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Track new scope separately, assess impact, reprioritize with stakeholders, and protect critical coverage.

Untracked scope makes test reports misleading.

scope creep changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

Report frequency, conditions, logs, data, timing, and any pattern observed.

Intermittent defects still count when impact is high.

intermittent issue changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.

They find the important risks early, communicate clearly, mentor others, improve coverage, and influence release decisions with evidence.

Seniority is judgment, not just years.

senior manual tester changes Manual Testing decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.