Skip to content

Manual Tester Interview Questions & Answers

40 questions for Manual Tester interviews — 25 easy, 15 medium.

About the Manual Tester role

A manual tester reads requirements, writes test scenarios and test cases, executes them on each build and logs clear bug reports. The role also covers exploratory testing, retesting and regression before releases. Interviews test core concepts, test case writing for common features like login or checkout, the bug life cycle, severity versus priority and basic SQL. Clear communication and attention to detail are judged throughout.

Test case writing Bug reporting Exploratory testing Basic SQL Jira
Solved for this roleStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
01

What does the absence-of-errors fallacy mean?

Save to ▾
Show answer
It means that finding and fixing many defects does not guarantee success if the system itself does not meet user needs. A bug-free product built on wrong or misunderstood requirements is still a failure. For example, a perfectly working report that shows the wrong business metric is useless to the client. This is why testers validate against real user expectations, not just the written specification.
02

What is software testing and why is it needed?

Save to ▾
Show answer
Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after release.
03

What is a test scenario for the login functionality at a high level?

Save to ▾
Show answer
Valid login, invalid login, forgot password, locked account and session handling are the main scenarios to cover.
04

What are latent defects and masked defects?

Save to ▾
Show answer
A latent defect exists in the software but has not caused a failure yet because the needed conditions have not occurred, such as a leap-year bug that appears only on 29 February. A masked defect is hidden by another defect, for example a broken discount calculation you cannot reach because the cart page crashes first. After the first bug is fixed, the masked one appears, which is one reason regression and retesting matter.
05

What is a regression bug and how do you track it in Jira?

Save to ▾
Show answer
A regression bug is a feature that worked before but broke after a new change, such as login failing after a profile page update. It is usually treated with higher priority because it affects existing users. In Jira, add a label such as regression, set the affected version and link it to the story or change that caused it. Tracking these labels over time shows where regression coverage is weak.
06

Why are you interested in a mobile testing role?

Save to ▾
Show answer
Model answer: Most users in India now use services first on their phones, so mobile quality directly affects customers. In my project I tested a college event app on four phones and found that the registration button was hidden by the keyboard on small screens. Fixing it raised sign-ups. I enjoy the variety of devices, networks and real-life situations that mobile testing involves.
07

What does quality mean to you as a tester?

Save to ▾
Show answer
Model answer: To me quality means the product does what users need, reliably, and is easy to use, not just that test cases pass. In my final-year project I tested a library app; all features worked, but students struggled to find the search option. I reported it as a usability issue and the team moved search to the home screen. That taught me to test from the user's point of view as well.
08

What is boundary value analysis?

Save to ▾
Show answer
Testing at the edges of input ranges, such as 17, 18 and 19 for an age limit of 18, since errors cluster at boundaries.
09

Difference between black box, white box and grey box testing?

Save to ▾
Show answer
Black box tests behaviour without code knowledge; white box tests internal logic and paths; grey box uses partial knowledge of the internals.
10

Write test cases for a multi-select dropdown.

Save to ▾
Show answer
1. Open and close by click and keyboard. 2. Select one, then several options; all show as chips or a count. 3. Deselect an option. 4. Select all and clear all, if available. 5. Search inside the list filters options. 6. Maximum selection limit is enforced with a message. 7. Required field shows an error if none selected. 8. Saved selection persists after refresh. 9. Long option names do not break layout. 10. Screen reader announces selected state.
11

When should you reopen a bug and when should you log a new one?

Save to ▾
Show answer
Reopen the bug when the same issue, with the same steps and expected result, still fails after the fix. Log a new bug when the fix works but a different problem appears, even in the same screen, or when the original bug has already been closed in a past release. Link the new bug to the old one. Mixing different problems in one reopened ticket confuses tracking and metrics.
12

What are severity and priority? Give examples.

Save to ▾
Show answer
Severity is impact on the system; priority is urgency of the fix. A crash in a rare report is high severity, low priority; a spelling mistake in the logo is low severity, high priority.
13

What is a duplicate bug and how do you avoid logging one?

Save to ▾
Show answer
A duplicate bug is a new report for a problem that is already logged. Before raising a bug, search the tracker by key words, module, error message and recent open bugs, and ask teammates working on the same area. If a similar bug exists, add your extra information, such as another browser or data set, as a comment instead of a new ticket. This keeps the backlog clean and saves triage time.
14

The developer says "it's not a bug". What do you do?

Save to ▾
Show answer
Re-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.
15

Write test cases for a date of birth field.

Save to ▾
Show answer
Verify a valid date is accepted and saved in the right format. Check the minimum age rule, such as 18 years, using boundary dates of exactly 18 today and one day short. Reject future dates and impossible dates like 30 February. Test leap year dates like 29 February 2004. Check manual typing and the picker give the same result, the field is mandatory if required, and the date displays correctly after saving.
16

Why is exhaustive testing impossible?

Save to ▾
Show answer
Exhaustive testing means trying every possible input, path and combination, which is practically infinite for real software. Even a single text field accepting 20 characters has more combinations than you could ever run. So testers use risk and techniques like equivalence partitioning and boundary value analysis to select a small set of tests that give high confidence. The goal is enough coverage of important risks, not every possible case.
17

What is the V-model?

Save to ▾
Show answer
A development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.
18

Write test cases for a signup form.

Save to ▾
Show answer
Mandatory fields, email format, password rules, duplicate email, terms checkbox, captcha, confirmation email and field length limits.
19

What is the difference between a build and a release?

Save to ▾
Show answer
A build is a compiled version of the software created from the latest code, often many times a day, and given to QA for testing. A release is a tested, approved version delivered to customers or production, usually with release notes and a version number. Many builds can go through testing before one of them is promoted as a release. Testers always note the build number in bug reports.
20

What is pairwise testing?

Save to ▾
Show answer
A technique that tests all pairs of input values instead of every combination, greatly reducing test cases while catching most defects.
21

What is UAT?

Save to ▾
Show answer
User Acceptance Testing — end users or the client verify that the system meets business needs in a production-like environment before go-live.
22

What is the difference between quality assurance and quality control?

Save to ▾
Show answer
Quality assurance is process-oriented and preventive: it sets standards, reviews and checklists so defects are not introduced in the first place. Quality control is product-oriented and detective: it checks the actual build through testing and inspection to find defects. For example, introducing a requirement review checklist is QA, while executing test cases on a release build is QC. Software testing is one activity inside quality control.
23

How do you write steps to reproduce for a bug that needs specific test data?

Save to ▾
Show answer
Start with preconditions: environment, build number, user role and the exact data state, such as an account with two pending orders and zero wallet balance. Mention how to create the data or give the test account ID. Then list numbered steps with exact inputs and finish with expected and actual results. If the data is hard to set up, attach the SQL used or a database screenshot so the developer can recreate it quickly.
24

Write test cases for a search box.

Save to ▾
Show answer
Valid keyword, partial match, no results, special characters, very long text, empty search, case sensitivity, spelling errors, suggestions and speed of results.
25

Severity vs priority — with an example.

Save to ▾
Show answer
Severity = impact on the system. Priority = urgency to fix. Logo misspelt on the homepage → low severity, high priority. Crash in a rarely used report → high severity, low priority.
26

Write test cases for a lift (elevator).

Save to ▾
Show answer
Moves to the chosen floor, doors open and close, door sensor stops closing on obstruction, overload alarm, emergency button, behaviour in a power cut, max capacity and the floor display.
27

Write a Gherkin scenario for applying a valid coupon at checkout.

Save to ▾
Show answer
Feature: Coupon at checkout Scenario: Valid coupon reduces the total Given I am logged in with 1000 rupees of items in my cart And the coupon 'SAVE10' gives 10 percent off When I apply the coupon 'SAVE10' Then the discount shown is 100 rupees And the order total is 900 rupees
28

What is the difference between a high-level and a low-level test case?

Save to ▾
Show answer
A high-level test case states what to test without detailed steps or exact data, for example 'Verify user can reset password using registered email'. A low-level test case gives exact steps, test data and expected results for each step. High-level cases are quick to write and suit experienced testers or changing features. Low-level cases suit regulated projects, new team members and cases that will later be automated.
29

Write test cases for an OTP verification screen.

Save to ▾
Show answer
Verify a correct OTP within validity logs the user in. Verify a wrong OTP shows an error and an expired OTP is rejected. Check the OTP length and that only digits are allowed. Test resend: it is disabled during the countdown, and the old OTP stops working after resend. Check the maximum number of wrong attempts locks verification. Verify auto-read on mobile, paste support, and behaviour when the network drops during submission.
30

Why is orientation and screen size testing important?

Save to ▾
Show answer
Mobile users have many screen sizes, resolutions, notches and foldable screens, and they rotate their phones. Rotation can recreate the screen and lose entered data if not handled. Test portrait and landscape on key screens, small and large phones and tablets, and check text does not cut off, buttons stay reachable and the keyboard does not hide input fields. Check entered form data survives rotation.
31

What is the difference between a test case and a test scenario?

Save to ▾
Show answer
A scenario is a high-level thing to test (user logs in); test cases are the detailed steps and data that verify it.
32

What are the boundary values for an age field that accepts 18–60?

Save to ▾
Show answer
Test 17, 18, 19, 59, 60 and 61.
33

How do you explain a technical bug to a non-technical stakeholder?

Save to ▾
Show answer
Focus on impact, not internals. Say who is affected, what they cannot do, how often it happens and what it may cost, for example: 'About one in twenty users paying by UPI see a failure message even though money is debited, which will raise refund complaints.' Then give the options and a recommendation. Avoid jargon like null pointer or race condition unless asked. A short screen recording often helps.
34

How do you handle it when a reviewer criticises your test cases?

Save to ▾
Show answer
I treat review comments as free help. I ask for specifics if a comment is unclear, fix valid points quickly and explain my reasoning if I disagree, with the requirement in hand. For example, a senior once said my cases missed negative paths; I added them and also made a personal checklist for future reviews. Repeated comments show me a skill gap I should work on, not a personal attack.
35

What is compliance testing?

Save to ▾
Show answer
Compliance testing checks that software meets external laws, standards or internal policies, not just functional requirements. Examples include payment security standards for card data, data protection rules for personal data, accessibility guidelines and RBI rules for banking apps. Testers verify items such as consent capture, data retention, audit logs and masking. Findings are usually documented as evidence for auditors, so traceability and clear records matter as much as the tests.
36

Write test cases for a calculator app.

Save to ▾
Show answer
Basic operations, division by zero, decimals, large numbers, order of operations, clear and backspace, repeated operations and memory keys.
37

How do you break a requirement into testable conditions?

Save to ▾
Show answer
Read the requirement and identify inputs, outputs, business rules, user roles and states. Turn each rule into a condition with an expected result, then add negative and boundary conditions. For example, 'users can withdraw up to 10,000 per day' becomes: withdraw below the limit, exactly at the limit, above the limit, multiple withdrawals adding up to the limit, and the limit resetting the next day. Each condition then becomes one or more test cases.
38

How would you test a pen?

Save to ▾
Show answer
First ask what type of pen and who the users are. Functional: it writes smoothly, ink flows without leaking, the cap or click mechanism works and the ink colour matches the label. Non-functional: comfort of grip, writing length before ink runs out, performance at different temperatures and on different paper. Negative: dropping it, pressing hard, leaving it uncapped. Safety: the cap is non-toxic and has an air hole. This shows structured thinking, not just a list.
39

What is the difference between Scrum and Kanban for a tester?

Save to ▾
Show answer
Scrum works in fixed sprints with planned scope, roles and ceremonies, so the tester plans testing for the sprint and aims to finish all stories by the sprint end. Kanban is a continuous flow with work-in-progress limits and no fixed sprints, so testing happens as each item reaches the test column. In Kanban, a tester watches that the testing column does not become a bottleneck and raises it when limits are hit.
40

What is a test case and its components?

Save to ▾
Show answer
A set of steps with inputs and expected results. Components: ID, title, preconditions, steps, test data, expected result, actual result and status.

Frequently asked questions

What does a Manual Tester do?

A manual tester reads requirements, writes test scenarios and test cases, executes them on each build and logs clear bug reports. The role also covers exploratory testing, retesting and regression before releases. Interviews test core concepts, test case writing for common features like login or checkout, the bug life cycle, severity versus priority and basic SQL. Clear communication and attention to detail are judged throughout.

Which skills are tested in a Manual Tester interview?

Expect questions on Test case writing, Bug reporting, Exploratory testing, Basic SQL, Jira. Most rounds also ask you to explain a project and solve one practical problem live.

How do I prepare for a Manual Tester interview?

Revise Manual Testing Basics, Test Case Design, Bug Life Cycle and Jira first using the topic sheets, practise the questions on this page aloud, then do one full mock interview to practise timing.