All 62 questions

  1. What types of software testing do you know, and when would you use each?

    Asked in 9 of 245 interviews · last asked Oct 19 · Concept · Junior

    Show answer

    Unit testing checks small code parts; integration testing checks how parts work together. System testing checks the complete product, while acceptance testing checks whether it meets user and business needs. Functional testing checks features; non-functional testing checks qualities like speed, security, and usability. Regression testing checks that changes have not broken existing behavior.

    • Smoke testing checks critical functions before deeper testing of a build.
    • Retesting checks whether a specific defect is fixed; regression testing looks for problems caused by changes.
    • Exploratory testing combines learning, test design, and execution to find problems beyond prepared test cases.
    • Testing levels describe scope; testing types describe purpose. Functional and non-functional tests can run at different levels.

    What the interviewer checks: The interviewer checks whether you understand testing levels and types and can choose them for the right purpose.

    Other ways it was asked
    • “What types of software testing do you know?”
    • “What are the different types of software testing?”
    • “How would you explain the different types of software testing, with examples?”
  2. What are verification and validation, and how do they differ?

    Asked in 7 of 245 interviews · last asked Oct 1 · Concept · Junior

    Show answer

    Verification checks whether a product meets its specified requirements. Validation checks whether it meets user needs and works for its intended use. In simple terms, verification asks, “Are we building the product right?” Validation asks, “Are we building the right product?”

    • Verification can use reviews and tests; it is not limited to checking documents.
    • Validation often includes testing real user tasks, such as acceptance testing.
    • A product can meet its specification but still fail to meet user needs.

    What the interviewer checks: The interviewer checks whether you understand the difference between meeting specifications and meeting user needs.

    Other ways it was asked
    • “What is the difference between verification and validation?”
    • “What is the difference between validation and verification?”
    • “What do you mean by verification and validation?”
  3. What is white-box testing, and how does it differ from black-box testing?

    Asked in 5 of 245 interviews · last asked Aug 25 · Concept · Junior

    Show answer

    White-box testing uses knowledge of the code to design tests for internal logic, such as conditions and branches. Black-box testing checks inputs and outputs against requirements without using knowledge of the code. White-box testing checks how the software works; black-box testing checks what it does.

    • White-box tests target code structure and logic.
    • Black-box tests target expected behavior from requirements.
    • Both approaches can find defects the other may miss.
    • White-box testing usually needs programming knowledge.

    What the interviewer checks: The interviewer is checking whether you understand how code knowledge changes test design.

    Other ways it was asked
    • “What is the difference between black-box and white-box testing?”
    • “Can you compare black-box testing and white-box testing?”
    • “Can you compare black-box and white-box testing?”
  4. How do unit, integration, and end-to-end tests differ, and when would you use each?

    Asked in 4 of 245 interviews · last asked Oct 22 · Concept · Junior

    Show answer

    Unit tests check one small piece of code in isolation; use them to check logic quickly. Integration tests check whether parts work together; use them to find problems between components. End-to-end tests check a complete user flow through the system; use them for important tasks such as signing in or buying an item.

    • Unit tests are usually fast and help locate bugs precisely.
    • Integration tests check connections, such as an application reading from a database.
    • End-to-end tests cover full workflows but are usually slower and harder to maintain.
    • Use many focused tests and fewer end-to-end tests for critical user flows.

    What the interviewer checks: The interviewer checks whether you understand each test level and can choose the right scope and cost.

    Other ways it was asked
    • “What is the difference between an integration test and an end-to-end test?”
    • “What is the difference between end-to-end tests and integration tests?”
    • “What are end-to-end tests, and when should you use them?”
  5. What is the difference between smoke, sanity, and regression testing?

    Asked in 4 of 245 interviews · last asked Oct 24 · Concept · Junior

    Show answer

    Smoke testing checks the main features to see if a build is ready for deeper testing. Sanity testing usually checks a specific change and closely related features. Regression testing checks that changes have not broken existing features. Teams may use these terms differently, especially sanity testing.

    • Smoke testing is broad but shallow and helps reject unstable builds early.
    • Sanity testing is narrow and focused, often after a small change or fix.
    • Regression testing covers areas at risk from changes; it does not always mean retesting everything.
    • These tests can overlap and can be manual or automated.
    Code
    After a change to checkout:
    Smoke: Check login, product search, and a basic purchase.
    Sanity: Check the changed checkout step and related behavior.
    Regression: Check existing discounts, payments, and order history.

    What the interviewer checks: The interviewer is checking whether you understand each test's purpose, scope, and when to use it.

    Other ways it was asked
    • “What’s the difference between smoke testing and sanity testing?”
    • “What is the difference between smoke testing and sanity testing?”
    • “What is the difference between regression testing and sanity testing?”
  6. Can you explain the software testing life cycle and how test cases fit into it?

    Asked in 4 of 245 interviews · last asked Sep 17 · Concept · Junior

    Show answer

    The software testing life cycle (STLC) is the process used to plan, prepare, run, and complete testing. Its main phases are requirement analysis, test planning, test case design, environment setup, test execution, and test closure. Test cases link requirements to steps and expected results; we run them, compare actual results, and report defects.

    • During test design, prepare test cases and test data, and review requirement coverage.
    • During execution, record pass or fail results, report defects, retest fixes, and run regression tests.
    • At closure, summarize results, unresolved defects, and lessons learned.
    • Phases can overlap or repeat, and test cases change when requirements change.

    What the interviewer checks: The interviewer checks whether you understand the testing process and how test cases support requirement coverage and execution.

    Other ways it was asked
    • “What is STLC, and what are its different phases?”
    • “What is STLC?”
    • “What is the STLC process?”
  7. What is the difference between functional and non-functional testing?

    Asked in 4 of 245 interviews · last asked Sep 24 · Concept · Junior

    Show answer

    Functional testing checks what the system does, such as whether login works correctly. Non-functional testing checks how well the system works, such as its speed, reliability, and ease of use. Both are needed because a feature can work correctly but still be slow or hard to use.

    • Functional requirements describe features and expected results; non-functional requirements describe quality goals and limits.
    • Functional tests compare actual results with expected behavior.
    • Non-functional tests assess qualities such as performance, usability, and reliability against defined criteria.
    • Both types can be tested manually, but some checks need tools, such as load testing.

    What the interviewer checks: The interviewer checks whether you can separate correct behavior from quality expectations and explain why both matter.

    Other ways it was asked
    • “What are functional and nonfunctional tests, and how do they differ?”
    • “What is the difference between functional and non-functional requirements?”
    • “What are the fundamental differences between functional and nonfunctional testing, and why do those distinctions matter in QA?”
  8. What is software testing?

    Asked in 4 of 245 interviews · last asked Oct 1 · Concept · Junior

    Show answer

    Software testing means checking software to find defects and see whether it meets requirements and user needs. It helps assess quality and reduce the risk of failures. The process includes reviewing requirements, planning tests, running them, comparing actual and expected results, and reporting defects.

    • Testing checks both stated requirements and real user needs.
    • Testing includes reviews without running software, as well as tests that run it.
    • Testing can find defects, but it cannot prove that no defects remain.
    • After fixes, testers check the fix and test for unintended effects.

    What the interviewer checks: The interviewer is checking whether you understand the purpose, basic activities, and limits of software testing.

    Other ways it was asked
    • “What is testing in software engineering?”
    • “What is software testing, and what does the testing process involve?”
    • “What is the actual definition and purpose of software testing?”
  9. Why do you think software testing is important?

    Asked in 2 of 245 interviews · last asked Jul 22 · Concept · Junior

    Other ways it was asked
    • “What is software testing and why is it important?”
  10. What is the shift-left testing approach?

    Asked in 2 of 245 interviews · last asked Aug 4 · Concept · Mid-level

    Other ways it was asked
    • “What is shift-left testing, and when would you use it?”
  11. What are the fundamentals of software testing?

    Asked in 2 of 245 interviews · last asked Oct 17 · Concept · Junior

    Other ways it was asked
    • “What are the principles of software testing?”
  12. What is the difference between positive and negative testing?

    Asked in 2 of 245 interviews · last asked Oct 3 · Concept · Junior

  13. What are the types of validation?

    Asked in 2 of 245 interviews · last asked Mar 26 · Concept · Junior

    Other ways it was asked
    • “What are the types of software validation?”
  14. What does quality mean to you in a digital product?

    Asked once · last asked Feb 9 · Concept

  15. What is the difference between statement coverage and branch coverage?

    Asked once · last asked Apr 10 · Concept · Mid-level

  16. What are test-first development, TDD, and ATDD, and when would you use each?

    Asked once · last asked May 21 · Concept · Mid-level

  17. What does BDD stand for, what tool is it associated with, and when and why would you use this approach?

    Asked once · last asked May 28 · Concept · Mid-level

    Other ways it was asked
    • “What does BDD stand for, what tool is it associated with, and when would you use it? What are its benefits?”
  18. How does your testing approach differ across frontend, middleware, and backend applications?

    Asked once · last asked Jun 26 · Concept · Mid-level

  19. What type of testing examines a product from the outside without knowledge of its internal design?

    Asked once · last asked Jul 16 · Concept · Junior

  20. Why might a team prioritize smoke and sanity testing over other types of testing for an application?

    Asked once · last asked Jul 16 · Scenario · Mid-level

  21. How can verification and validation activities be carried out in parallel?

    Asked once · last asked Jul 16 · Scenario · Mid-level

  22. If module A is built and module B is under development, how will you perform integration testing between them?

    Asked once · last asked Jul 16 · Scenario · Mid-level

  23. What is regression testing and when do you run it?

    Asked once · last asked Jul 22 · Concept · Junior

  24. What are smoke, regression, integration, and system testing?

    Asked once · last asked Jul 27 · Concept · Junior

  25. In a Waterfall project, when is work ready to move to testing, and where is the Waterfall model still used today?

    Asked once · last asked Aug 4 · Concept · Mid-level

  26. After a pull request is submitted, how should a frontend tester review it and decide whether to approve it or leave comments?

    Asked once · last asked Aug 5 · Scenario · Mid-level

  27. What is the difference between system testing and integration testing, and can you give a practical example of each?

    Asked once · last asked Aug 23 · Concept · Junior

  28. Do you think that API testing is always integration testing?

    Asked once · last asked Aug 25 · Concept · Mid-level

  29. What is the difference between quality assurance and testing, and what are the main types of testing?

    Asked once · last asked Sep 17 · Concept · Junior

  30. How can a team detect regressions when a code change breaks another module?

    Asked once · last asked Oct 2 · Scenario · Senior

  31. What is the difference between localization and internationalization?

    Asked once · last asked Oct 17 · Concept · Junior

  32. What is the difference between regression testing and retesting?

    Asked once · last asked Oct 24 · Concept · Junior

  33. What is mutation testing, and what does a low mutation score indicate?

    Asked once · last asked Oct 24 · Concept · Mid-level

  34. What is security testing, and what does it involve?

    Asked once · last asked Aug 4 · Concept · Junior

  35. Can you give an example of a high-quality digital product and explain why, and one you consider low quality?

    Asked once · last asked Feb 9 · Scenario

  36. What is testing in the waterfall methodology?

    Asked once · last asked Mar 26 · Concept · Junior

  37. What are the types of testing, such as unit, integration, and system testing?

    Asked once · last asked Mar 26 · Concept · Junior

  38. What is testing?

    Asked once · last asked Mar 26 · Concept · Junior

  39. In software engineering, what does validation mean?

    Asked once · last asked Mar 26 · Concept · Junior

  40. What can happen if testing is omitted from the software development life cycle?

    Asked once · last asked Mar 27 · Concept · Junior

  41. When do you validate the program, and when do you verify the product?

    Asked once · last asked Apr 30 · Concept · Junior

  42. What is a bug in software testing?

    Asked once · last asked May 8 · Concept · Junior

  43. What is a review in software testing?

    Asked once · last asked May 8 · Concept · Junior

  44. What activities are involved in a formal software review?

    Asked once · last asked May 8 · Concept · Junior

  45. What types of testing do you perform during software development?

    Asked once · last asked May 21 · Concept · Mid-level

  46. What is one key distinction between functional testing and regression testing, and why is that distinction important?

    Asked once · last asked Jun 8 · Concept · Junior

  47. What do you verify when testing a software application?

    Asked once · last asked Jun 10 · Concept

  48. What does it mean for a test to be repeatable, and why is that important?

    Asked once · last asked Jun 12 · Concept · Junior

  49. Why do we perform regression testing?

    Asked once · last asked Jul 16 · Concept · Junior

  50. Why would you write unit and functional tests?

    Asked once · last asked Jul 17 · Concept · Junior

  51. What does ISTQB represent in software testing?

    Asked once · last asked Jul 21 · Concept · Junior

  52. When does quality assurance typically take place in a Waterfall project?

    Asked once · last asked Aug 4 · Concept · Junior

  53. What does good testing look like?

    Asked once · last asked Aug 19 · Concept · Mid-level

  54. What is the Software Testing Life Cycle (STLC)?

    Asked once · last asked Aug 25 · Concept · Junior

  55. Can you give me an example of the manual work you’d do as a QA Engineer?

    Asked once · last asked Sep 2 · Scenario · Junior

  56. In a senior QA role, how would you define quality?

    Asked once · last asked Sep 11 · Concept · Senior

  57. What is smoke testing?

    Asked once · last asked Sep 17 · Concept · Junior

  58. What is Quality Control (QC)?

    Asked once · last asked Oct 1 · Concept · Junior

  59. How many software testing principles are there? Name the ones you remember.

    Asked once · last asked Oct 3 · Concept · Junior

  60. What is sanity testing?

    Asked once · last asked Oct 3 · Concept · Junior

  61. What are the different types of software reviews?

    Asked once · last asked Oct 19 · Concept · Junior

  62. What are software testing and test automation?

    Asked once · last asked Oct 22 · Concept · Junior

More Manual Testing interview questions

How this list is made

Every question here was asked by a real interviewer in a real job interview that a candidate ran MeetAssist in. After the call, the interviewer's questions are pulled from the transcript. Practice sessions, tests, exams and anything that was not a job interview are dropped.

Questions are rewritten so they make sense on their own: names of people, employers and clients are removed, and speech-to-text mistakes are fixed. Small talk, logistics and questions about one candidate's own résumé are left out. Rephrasings of the same question are merged, and the count is the number of different interviews it came up in.

The interviews come from candidates who use MeetAssist, so they lean towards software, data and AI roles: the shares describe these interviews, not every Manual Testing interview. Answers to the most asked questions are written and checked by an editor; a "common mistake" is shown only when reviews of real answers in these interviews show it, with the count.

245 interviews, 143 candidates, Jan 2026 to Oct 2026. Updated every month with new interviews.