Manual testing interview questions: answers checked against the ISTQB syllabus
The software testing questions QA analysts and testers get, answered in plain words and checked against the ISTQB Foundation Level syllabus.
Manual testing interviews cover errors, defects and failures, verification versus validation, the seven testing principles, test levels and types, confirmation versus regression testing, equivalence partitioning and boundary value analysis, decision tables, state transitions, test cases, defect reports, severity versus priority, error guessing, exploratory testing and entry and exit criteria. Below are 13 questions; each answer lists the ISTQB syllabus it was checked against.
Basic manual testing interview questions
Basic1. What is the difference between an error, a defect and a failure?
A person makes an error (a mistake), which introduces a defect (a fault or bug) into code or a document. When defective code runs, it may cause a failure: the system does something it should not, or fails to do something it should. Not every defect causes a failure, for example if the code path is never executed.
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Basic2. What is the difference between verification and validation?
Verification checks that the system meets its specified requirements: are we building it right? Validation checks that it meets users' and other stakeholders' real needs in its environment: are we building the right thing? A product can pass verification and still fail validation if the requirements were wrong.
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Basic3. What are the seven principles of testing?
From the ISTQB Foundation syllabus: testing shows the presence of defects, not their absence; exhaustive testing is impossible; early testing saves time and money; defects cluster together; tests wear out (repeating the same tests finds fewer new defects); testing is context dependent; and the absence-of-defects fallacy (verifying the software does not ensure the system succeeds). Be ready to give an example for two or three of them.
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Basic4. What are the test levels?
Component (unit) testing checks components in isolation, usually by developers. Component integration and system integration testing check the interfaces between components or systems. System testing checks the whole system's behavior, including end-to-end tasks and quality characteristics. Acceptance testing, ideally by the intended users, validates that the system is ready to deploy; its forms include user acceptance testing (UAT).
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Basic5. What is the difference between functional and non-functional testing?
Functional testing checks what the system does: its functions are complete and correct. Non-functional testing checks how well it does it: performance, usability, security, reliability, compatibility and other quality characteristics. Manual testers often cover usability and exploratory checks, while performance testing usually needs tools.
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Intermediate manual testing interview questions
Intermediate6. What is the difference between retesting (confirmation testing) and regression testing?
Confirmation testing reruns the failed test after a fix to check that the defect is really fixed. Regression testing checks that the change did not break anything else, in the same component or elsewhere. Regression suites are run often, so they are the usual first candidates for automation.
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Intermediate7. What are equivalence partitioning and boundary value analysis?
Equivalence partitioning splits inputs into groups the system should treat the same way, valid and invalid, and tests one value from each group. Boundary value analysis tests the edges of those groups, where defects are common. For an age field that accepts 18 to 65: partitions are below 18, 18 to 65, and above 65; boundary values include 17, 18, 65 and 66.
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Intermediate8. What is decision table testing?
A technique for rules that combine several conditions: list the conditions and actions, then write one column (rule) for each combination that matters, and design a test for each column. It exposes missing or contradictory rules in the requirements.
Example decision table snippet · illustrative, not run on this pageConditions R1 R2 R3 R4
Member? Y Y N N
Order over $50? Y N Y N
Actions
Free shipping Y Y Y N
Discount 10% Y N N NChecked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Intermediate9. What is state transition testing?
Model the system as states and the events that move it between them, with any conditions (guards), then design tests that cover the states and transitions, including invalid transitions that should be rejected. It suits workflows such as an order moving from placed to paid to shipped, or a login that locks after three failures.
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Intermediate10. How do you write a good test case?
Give it a clear purpose and a link to the requirement it covers, preconditions and test data, numbered steps that someone else can follow, and an expected result for each check. Keep one objective per test case so a failure points to one problem.
Example test case snippet · illustrative, not run on this pageID: TC-LOGIN-004
Requirement: REQ-AUTH-2 (lock after 3 failed attempts)
Precondition: active account test.user@example.com
Steps: 1. Enter a wrong password three times 2. Enter the correct password
Expected: after step 1, the message says the account is locked; after step 2, login is refusedChecked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Advanced manual testing interview questions
Advanced11. What should a defect report contain, and what is the difference between severity and priority?
A unique ID, a short descriptive title, the test object and environment (build, browser, device), steps to reproduce, expected and actual results, evidence such as screenshots or logs, severity and priority. Severity is the impact of the defect; priority is how soon it should be fixed. A typo on the home page can be low severity but high priority; a crash in a rarely used admin report can be high severity but lower priority.
Example defect report snippet · illustrative, not run on this pageTitle: Checkout total ignores 10% member discount
Environment: build 4.12.0, Chrome 157, staging
Steps: 1. Log in as member 2. Add a $60 item 3. Open checkout
Expected: total $54.00 Actual: total $60.00
Severity: major Priority: highChecked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Advanced12. What are error guessing and exploratory testing?
Error guessing uses the tester's knowledge of past failures and common developer mistakes to target likely defects, such as empty inputs, special characters or double submissions. In exploratory testing, the tester designs, runs and evaluates tests at the same time while learning the product, often in time-boxed sessions with a charter. Both complement scripted tests.
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
Advanced13. What are entry and exit criteria?
Entry criteria are the preconditions for starting a test activity, such as a stable build deployed to the test environment and test data ready. Exit criteria define when it is complete, such as planned tests run, no open critical defects, and agreed coverage reached. Interviewers often ask what you do when time runs out before exit criteria are met: report the remaining risk so the team can decide.
Checked against: ISTQB Certified Tester Foundation Level syllabus v4.0.1
How to practice with this page
- Apply EP and BVA to a real form field and list your test values.
- Write one defect report for a bug you found, with clear steps.
- Prepare a story about a defect you found by exploratory testing.
- Learn basic SQL and API testing to check data behind the screen.
Related interview prep and tools
API testing questions.
Open →QuestionsPlaywright interview questionsModern browser automation, with real output.
Open →RoleQA tester interview questionsRole questions for QA testers and analysts.
Open →Free toolResume summary generatorDraft a summary for a QA Analyst role; the title is filled in, you add your experience.
Open →Free toolLinkedIn headline generatorWrite a headline for a QA Analyst search.
Open →Disclosure: TryHired makes HIRED, a paid job-search program, so we have a conflict of interest when we mention it. This question bank is free, with no TryHired signup.
Questions people ask
What manual testing topics come up often in QA interviews?
Do I need the ISTQB certification for a manual testing job?
Should manual testers learn automation?
How this page is built
TryHired wrote these questions and answers. Statements about the technology were checked against the official documentation pages listed below, saved when the page was built (2026-11-16). The code snippets are short illustrations and were not run on this page. The question list is general practice: it does not predict what a particular employer will ask.
- Interviewers ask different questions for different roles and levels.
- Answers are short explanations, not complete references.
- The answers follow the ISTQB Certified Tester Foundation Level syllabus v4.0.1 (2024). Teams use their own terms; explain the idea if an interviewer uses a different word.
- ISTQB Certified Tester Foundation Level syllabus v4.0.1 (read 2026-11-15)