SoftwareTestPilot
Manual TestingPublished: 17 min read

Manual Testing Interview Questions PDF: 30 Q&A to Revise

Manual testing interview questions and answers you can save as a PDF: 30 questions on STLC, test design, bugs, Agile and scenarios, plus a 7-day revision plan.

SoftwareTestPilot
QA Editorial Team
Share:XLinkedInWhatsApp
Manual Testing Interview Questions PDF: 30 Q&A to Revise: Manual Testing article cover, SoftwareTestPilot.com
Manual Testing Interview Questions PDF: 30 Q&A to Revise: Manual Testing article cover, SoftwareTestPilot.com

If you searched for a manual testing interview questions PDF download, you probably want one reliable document you can read on the bus, print the night before, or mark up with a pen. This page is built for that. It has 30 manual testing interview questions with short, correct answers and examples, grouped in the order most interviews follow. You can turn it into a PDF in a few seconds (steps below), and if you want a longer designed PDF, section 1 lists the real ones in our library.

Definitions follow the ISTQB Foundation Level (CTFL v4.0) syllabus, which most Indian and international interviewers treat as the common vocabulary, written here in plain English rather than copied wording.

1. How to Download This as a PDF (and Which PDF to Choose)

Option A: Save this page as a PDF (free)

  1. Open this article on a laptop or desktop.
  2. Press Ctrl+P (Windows/Linux) or Cmd+P (Mac).
  3. Set the destination to Save as PDF and click Save.

On a phone, open the browser menu, choose Share or Print, then Save as PDF. The 30 questions fit on roughly 12 to 15 printed pages depending on your browser settings.

Option B: Longer PDFs in the QA Notes Vault

If you want more questions in a designed document, these manual testing PDFs are in our library. You can preview the first pages of each before deciding:

Option A is enough for a quick revision. Pick a Vault PDF only if you want more volume or depth.

Before you trust any PDF you find online

Many free manual testing PDFs shared on forums and messaging groups are years old or copied from each other. Spend two minutes checking these before you memorise anything:

CheckRed flag
Testing principlesLists "pesticide paradox" without explaining that tests need updating; v4.0 calls this "tests wear out".
Severity vs prioritySays "the tester always sets both" with no mention of business input.
Test levelsMissing component integration vs system integration, or no acceptance testing types.
AgileNo mention of sprints, user stories or acceptance criteria at all.
AnswersOne-line definitions with no example; you will not be able to defend them in a follow-up.

2. Testing Basics (Questions 1 to 6)

Q1: What is software testing?

Answer: Software testing is the set of activities used to find defects and to evaluate the quality of a product, so the team can reduce the risk of failures in use. It includes checking that the software meets its requirements (verification) and that it meets the user's real needs (validation). It is more than running tests: it includes planning, analysis, design, reviews and reporting.

Q2: What is manual testing, and when is it still the right choice?

Answer: Manual testing means a person executes tests and judges the result without automation scripts. It is the right choice for exploratory testing, usability and look-and-feel checks, features that change every sprint, and one-off checks where writing a script costs more than running it a few times. Stable, repetitive regression checks are better automated.

Q3: Verification vs validation?

Answer: Verification asks "are we building the product right?", checking work products against specifications, often through reviews. Validation asks "are we building the right product?", checking that the product meets the user's needs, usually by executing it. Example: reviewing a login requirement document is verification; a user trying to log in during acceptance testing is validation.

Q4: Error vs defect vs failure?

Answer: A person makes an error (a mistake), which can introduce a defect (a bug) in code or a document. When defective code runs and the system does something wrong, that is a failure. Example: a developer misreads "minimum 8 characters" as 6 (error), writes the check as length >= 6 (defect), and the app accepts a 6-character password (failure).

Q5: What are the seven testing principles?

Answer: (1) Testing shows the presence, not the absence, of defects. (2) Exhaustive testing is impossible. (3) Early testing saves time and money. (4) Defects cluster together. (5) Tests wear out, so they must be updated. (6) Testing is context dependent. (7) The absence-of-defects fallacy: a bug-free product that does not meet user needs is still a failure.

Q6: What is quality assurance vs quality control?

Answer: QA is process-focused and preventive: improving how the team works so fewer defects are made (reviews, standards, process audits). QC is product-focused and corrective: finding defects in what was built, mainly through testing. Testing is a form of quality control.

3. SDLC, STLC and Test Levels (Questions 7 to 12)

Q7: What is the STLC?

Answer: The Software Testing Life Cycle is the sequence of testing activities: requirement analysis, test planning, test case design, test environment setup, test execution and test closure. Each phase has entry and exit criteria. We explain each phase with deliverables in our STLC stages guide.

Q8: How does the STLC relate to the SDLC?

Answer: The SDLC covers the whole product life cycle (requirements, design, build, test, deploy, maintain). The STLC runs inside it. In good teams testing starts at requirements, not after coding: testers review stories and design tests while developers build.

Q9: What are the test levels?

Answer: Component (unit) testing, component integration testing, system testing, system integration testing and acceptance testing. Each level has its own objective and usually a different owner, for example developers own unit tests and business users often own acceptance testing.

Q10: What are entry and exit criteria?

Answer: Entry criteria are conditions that must be true before an activity starts, such as "build deployed to QA and smoke test passed". Exit criteria define when it is done, such as "all high-priority cases executed, no open critical defects, coverage target met". They stop testing from starting too early or ending on a feeling.

Q11: What is a test plan, and what goes in it?

Answer: A test plan describes the scope, approach, resources and schedule for testing. Typical sections: objectives, in-scope and out-of-scope items, test levels and types, environments, entry and exit criteria, risks and mitigations, deliverables, roles and schedule.

Q12: Test strategy vs test plan?

Answer: A test strategy is the high-level approach for an organisation or product, for example "risk-based, automate regression, manual exploratory each sprint". A test plan applies that approach to a specific release or project with dates, people and scope.

4. Test Cases and Test Design (Questions 13 to 18)

Q13: Test scenario vs test case?

Answer: A scenario is a one-line "what to test", such as "Verify login with valid credentials". A test case is the detailed "how": ID, preconditions, steps, test data and expected result. One scenario usually becomes several test cases. See 15 worked pairs in test scenario vs test case examples.

Q14: What makes a good test case?

Answer: It tests one thing, can run independently, has specific test data and a single clear expected result, and is traceable to a requirement. Anyone on the team should be able to run it and reach the same verdict.

Q15: What is equivalence partitioning?

Answer: Dividing inputs into groups (partitions) that the system should treat the same way, then testing one value from each. Example: age field accepts 18 to 60. Partitions: below 18 (invalid), 18 to 60 (valid), above 60 (invalid). Test 10, 35 and 70.

Q16: What is boundary value analysis?

Answer: Testing at the edges of partitions, because defects often sit there. With 2-value BVA for 18 to 60, test 17, 18, 60 and 61. With 3-value BVA, also test 19 and 59. Our boundary value analysis examples show more cases.

Q17: When do you use a decision table?

Answer: When the outcome depends on combinations of conditions. Example: free delivery if the user is a member and the order is above ₹500. Two conditions give four combinations; each column of the table becomes a test case, so no combination is missed.

Q18: What is a traceability matrix?

Answer: A table mapping each requirement to its test cases (and often to defects). It proves every requirement has tests, shows the impact when a requirement changes, and helps report coverage at release time.

5. Bugs and Defect Management (Questions 19 to 23)

Q19: Explain the bug life cycle.

Answer: A common flow is New → Assigned → Open → Fixed → Retest → Closed. Side paths include Rejected (not a bug), Duplicate, Deferred (fix later) and Reopened (the fix did not work). Exact states depend on the team's tool workflow, so mention the one you used. Walk through a full workflow in the bug life cycle guide.

Q20: Severity vs priority?

Answer: Severity is the technical impact of the defect on the system; priority is how soon it should be fixed. The tester usually proposes severity, and the product owner or lead decides priority based on business needs. Examples: company logo misspelled on the home page is low severity, high priority. A crash in a rarely used admin report is high severity, possibly lower priority. More examples are in 30 severity vs priority examples.

Q21: What goes into a good bug report?

Answer: A specific title, environment and build, preconditions, numbered steps to reproduce, expected result, actual result, severity, and evidence such as a screenshot, video or log. Write it so a developer can reproduce it without asking you a question.

Q22: Retesting vs regression testing?

Answer: Retesting runs the failed test again to confirm a specific fix works. Regression testing checks that the change did not break anything that worked before. Retesting is targeted at one defect; regression covers the surrounding and related areas.

Q23: What do you do if a developer says "it's not a bug"?

Answer: Go back to the source: the requirement, acceptance criteria or design. If the behaviour contradicts it, show that with evidence. If the requirement is silent or unclear, raise it with the product owner rather than arguing. The goal is the right product, not winning the discussion.

6. Testing Types and Agile (Questions 24 to 27)

Q24: Smoke testing vs sanity testing?

Answer: Smoke testing is a quick, broad check that a new build's key functions work and it is stable enough for further testing. Sanity testing is a quick, narrow check of a specific area after a small change or fix. Teams use these terms slightly differently, so describe how your team used them.

Q25: Functional vs non-functional testing?

Answer: Functional testing checks what the system does against its requirements, such as "the user can reset a password". Non-functional testing checks how well it does it: performance, usability, security, compatibility, reliability.

Q26: What is the tester's role in Scrum?

Answer: In Scrum, testers are part of the Developers. They help refine stories and acceptance criteria, estimate testing effort, test stories within the sprint, run regression, take part in the review and retrospective, and help decide whether a story meets the Definition of Done.

Q27: What is exploratory testing?

Answer: Testing where learning, test design and execution happen at the same time, guided by a charter such as "explore checkout with invalid coupons for 45 minutes". It finds issues scripted cases miss. Good testers time-box sessions and note what they covered and found.

7. Scenario Questions (Questions 28 to 30)

Q28: How would you test a login page?

Answer: Functional: valid login, invalid password, unregistered email, empty fields, password masking, remember-me, forgot password. Boundary: minimum and maximum password length. Security: account lock after failed attempts, error messages that don't reveal which field was wrong, HTTPS, SQL injection in fields, session timeout. UI and compatibility: browsers, mobile, keyboard navigation. Our login page test case guide lists 40 written examples.

Q29: You have one day to test a release that needs a week. What do you do?

Answer: Use risk-based testing. List features by business impact and likelihood of failure, test the critical paths first (login, payment, core flow), run a smoke and targeted regression around the changes, and tell stakeholders clearly what was not tested and the risk that remains. Never silently skip areas.

Q30: A bug was found in production that you missed. How do you respond?

Answer: First help contain it: reproduce it, give clear steps and impact. Then find why it escaped (missing test case, unclear requirement, environment difference, data not covered). Add a test to prevent a repeat and share the learning in the retrospective. Interviewers want ownership, not blame.

8. Worked Example: Turning a PDF Answer Into an Interview Answer

A PDF gives you the definition. An interviewer listens for whether you have used it. Here is how one answer changes when you add context. The project details are an illustrative example; replace them with your own.

Question: "What is boundary value analysis?"

PDF-style answer (weak on its own): "Testing at the boundaries of input ranges."

Interview answer (strong): "It's testing at the edges of valid and invalid ranges, because that's where off-by-one mistakes happen. For example, on a practice e-commerce app the quantity field allowed 1 to 10. I tested 0, 1, 10 and 11. The app accepted 11, because the check used 'greater than 11' instead of 'greater than 10'. I logged it with the steps and a screenshot, and after the fix I retested all four values."

The strong answer has the same definition, plus a reason, concrete values, a result and what you did next. Do this for at least ten questions in this list and your PDF becomes a set of stories rather than a set of lines.

QuestionWeak answerWhat makes it strong
Severity vs priority"Severity is impact, priority is urgency."Two contrasting examples and who decides each.
Bug life cycleA list of states.The tool you used and one bug you reopened, and why.
Regression testing"Testing after changes."How you chose which cases to run with limited time.
Exploratory testing"Testing without test cases."A charter, a time box and one thing it found.

9. Which Questions to Focus On for Your Experience Level

ExperienceFocus onExpect follow-ups like
FresherQ1 to Q5, Q7, Q13 to Q16, Q19 to Q22, Q28"Write test cases for this pen / lift / login page."
1 to 3 yearsAll 30, especially Q17, Q18, Q23, Q26, Q29"Show a bug you raised. How did you choose regression cases?"
3+ yearsQ10 to Q12, Q20, Q23, Q29, Q30"How do you plan testing for a release? How do you handle missed defects?"

Freshers can practise these by level with timed questions on our Interview Prep page. For a broader bank of more than 70 questions, read our complete manual testing interview questions and answers, and for "how would you test this?" rounds, see scenario-based testing interview questions.

10. Practice Exercise (With Answer)

Task: A "Apply coupon" field on a checkout page accepts codes of 6 to 12 letters and numbers. A coupon only works if the cart total is at least ₹999 and the coupon has not expired. Write five test cases an interviewer would accept, naming the technique each one uses.

Show a model answer
  1. BVA: 5-character code is rejected with a clear message; 6-character valid code is accepted.
  2. BVA: 12-character valid code is accepted; 13-character code is rejected.
  3. Equivalence partitioning: code with a special character (e.g. SAVE@10) is rejected.
  4. Decision table: valid, unexpired code with cart total ₹998 is rejected; same code with ₹999 is accepted.
  5. Decision table / negative: expired code with cart total ₹1,500 is rejected with an "expired" message, not a generic error.

Bonus points in an interview: mention case sensitivity, leading or trailing spaces, applying the same coupon twice, and what happens when an item is removed and the total drops below ₹999 after the coupon was applied.

11. A 7-Day Revision Plan for Your PDF

About an hour a day is enough.

  1. Day 1: Q1 to Q6. Say each answer aloud before reading it.
  2. Day 2: Q7 to Q12. Draw the STLC from memory with one deliverable per phase.
  3. Day 3: Q13 to Q18. Write test cases for one form using EP, BVA and a decision table.
  4. Day 4: Q19 to Q23. Write one full bug report for a real issue you find on any website.
  5. Day 5: Q24 to Q27. Run one 30-minute exploratory session with a written charter.
  6. Day 6: Q28 to Q30 plus the practice exercise. Time yourself: two minutes per scenario.
  7. Day 7: Mock round. Ask a friend to pick ten random questions, or post your answers in the community for feedback.

If you prefer short lessons over a document, the free QA Interview Crash Course covers theory and scenario rounds in about 50 minutes, and Test Cases and Bug Reports helps if Day 3 or Day 4 feels hard.

12. Final Checklist Before the Interview

  • I can explain error, defect and failure with one example.
  • I can name the seven testing principles.
  • I can draw the STLC and the bug life cycle from memory.
  • I can give two contrasting severity vs priority examples.
  • I can apply EP and BVA to any numeric field in under a minute.
  • I know the difference between retesting and regression testing.
  • I have one test case and one bug report of my own to show.
  • I can answer "how would you test a login page?" in a structured way.

Next step: save this page as a PDF now, then join the SoftwareTestPilot QA Community and share your answer to the practice exercise. Other testers can tell you what an interviewer would push back on.

Key takeaways

  1. 1Revise by topic: basics, SDLC and STLC, test design, bugs, Agile, then scenarios.
  2. 2Every answer should have three parts: what it is, why it matters, one example.
  3. 3Severity vs priority, the bug life cycle and boundary values come up in almost every round.
  4. 4Save this page as a PDF from your browser; it prints cleanly with headings and tables.
  5. 5Check any PDF you download elsewhere for outdated definitions before you memorise it.

Common mistakes to avoid

  • Memorising PDF answers word for word and sounding scripted.
  • Giving definitions with no example from a real or practice project.
  • Saying severity and priority are always set by the same person.
  • Confusing retesting with regression testing.
  • Answering scenario questions with only positive test cases.

Interview tips

  • 1Answer in three parts: definition, why it matters, a short example.
  • 2For 'how would you test X' questions, cover positive, negative, boundary, UI, security and compatibility checks.
  • 3If you are unsure of exact syllabus wording, explain the idea in your own words; interviewers value understanding over recitation.
  • 4Bring one test case and one bug report you wrote (from practice if you have no job yet) to talk through.

References

  1. 1
  2. 2
    ISTQB Glossary— glossary.istqb.org
  3. 3
    The Scrum Guide— scrumguides.org