Testing Concepts interview questions — Easy
125 easy-level Testing Concepts questions from our Manual Testing bank, each with the correct answer and an explanation of why it is correct.
This topic slice is available to practise but is not yet part of our indexed set.
What this covers
Testing Concepts appears throughout Manual Testing interviews. At easy level, interviewers are typically checking that you know the fundamentals and can describe them precisely — definitions, defaults, and the basic mechanics. Work through these, then explain your answer out loud; the second part is what interviews actually test.
20 example questions
1. In the context of Concepts, error, defect, failure is best described as:
- A. Human mistake → flaw in artifact → observable wrong behavior.correct
- B. Testing that executes the software.
- C. Documents from which test cases are derived.
- D. Author-led informal review of a work product.
Why: error, defect, failure: Human mistake → flaw in artifact → observable wrong behavior.
2. Which of the following best describes error, defect, failure in Concepts?
- A. Documents from which test cases are derived.
- B. Human mistake → flaw in artifact → observable wrong behavior.correct
- C. Testing that executes the software.
- D. Formal, moderated review with defined roles and metrics.
Why: error, defect, failure: Human mistake → flaw in artifact → observable wrong behavior.
3. Which of the following best describes static analysis in Concepts?
- A. Linking requirements to tests and defects.
- B. Documents from which test cases are derived.
- C. Tool-based examination of code without executing it.correct
- D. Author-led informal review of a work product.
Why: static analysis: Tool-based examination of code without executing it.
4. Which of the following best describes inspection in Concepts?
- A. Tool-based examination of code without executing it.
- B. Formal, moderated review with defined roles and metrics.correct
- C. Testing that executes the software.
- D. Developer activity of locating and fixing defect causes.
Why: inspection: Formal, moderated review with defined roles and metrics.
5. Which of the following best describes dynamic testing in Concepts?
- A. Testing that executes the software.correct
- B. Documents from which test cases are derived.
- C. Author-led informal review of a work product.
- D. Formal, moderated review with defined roles and metrics.
Why: dynamic testing: Testing that executes the software.
6. What is the purpose of error, defect, failure in Concepts?
- A. Developer activity of locating and fixing defect causes.
- B. Tool-based examination of code without executing it.
- C. Linking requirements to tests and defects.
- D. Human mistake → flaw in artifact → observable wrong behavior.correct
Why: error, defect, failure: Human mistake → flaw in artifact → observable wrong behavior.
7. What is the purpose of debugging in Concepts?
- A. Tool-based examination of code without executing it.
- B. Formal, moderated review with defined roles and metrics.
- C. Documents from which test cases are derived.
- D. Developer activity of locating and fixing defect causes.correct
Why: debugging: Developer activity of locating and fixing defect causes.
8. What is the purpose of static analysis in Concepts?
- A. Tool-based examination of code without executing it.correct
- B. Documents from which test cases are derived.
- C. Human mistake → flaw in artifact → observable wrong behavior.
- D. Testing that executes the software.
Why: static analysis: Tool-based examination of code without executing it.
9. Which of the following best describes traceability in Concepts?
- A. Documents from which test cases are derived.
- B. Linking requirements to tests and defects.correct
- C. Human mistake → flaw in artifact → observable wrong behavior.
- D. Testing that executes the software.
Why: traceability: Linking requirements to tests and defects.
10. Which of the following best describes walkthrough in Concepts?
- A. Linking requirements to tests and defects.
- B. Formal, moderated review with defined roles and metrics.
- C. Testing that executes the software.
- D. Author-led informal review of a work product.correct
Why: walkthrough: Author-led informal review of a work product.
11. What is the purpose of inspection in Concepts?
- A. Developer activity of locating and fixing defect causes.
- B. Human mistake → flaw in artifact → observable wrong behavior.
- C. Formal, moderated review with defined roles and metrics.correct
- D. Documents from which test cases are derived.
Why: inspection: Formal, moderated review with defined roles and metrics.
12. Which of the following best describes debugging in Concepts?
- A. Developer activity of locating and fixing defect causes.correct
- B. Linking requirements to tests and defects.
- C. Author-led informal review of a work product.
- D. Documents from which test cases are derived.
Why: debugging: Developer activity of locating and fixing defect causes.
13. In Concepts, what does inspection do or refer to?
- A. Tool-based examination of code without executing it.
- B. Formal, moderated review with defined roles and metrics.correct
- C. Human mistake → flaw in artifact → observable wrong behavior.
- D. Testing that executes the software.
Why: inspection: Formal, moderated review with defined roles and metrics.
14. In Concepts, what does static analysis do or refer to?
- A. Human mistake → flaw in artifact → observable wrong behavior.
- B. Developer activity of locating and fixing defect causes.
- C. Formal, moderated review with defined roles and metrics.
- D. Tool-based examination of code without executing it.correct
Why: static analysis: Tool-based examination of code without executing it.
15. In Concepts, what does debugging do or refer to?
- A. Author-led informal review of a work product.
- B. Testing that executes the software.
- C. Developer activity of locating and fixing defect causes.correct
- D. Documents from which test cases are derived.
Why: debugging: Developer activity of locating and fixing defect causes.
16. Which of the following best describes test basis in Concepts?
- A. Human mistake → flaw in artifact → observable wrong behavior.
- B. Documents from which test cases are derived.correct
- C. Author-led informal review of a work product.
- D. Tool-based examination of code without executing it.
Why: test basis: Documents from which test cases are derived.
17. In Concepts, what does test basis do or refer to?
- A. Documents from which test cases are derived.correct
- B. Testing that executes the software.
- C. Author-led informal review of a work product.
- D. Tool-based examination of code without executing it.
Why: test basis: Documents from which test cases are derived.
18. In Concepts, what does walkthrough do or refer to?
- A. Documents from which test cases are derived.
- B. Author-led informal review of a work product.correct
- C. Developer activity of locating and fixing defect causes.
- D. Formal, moderated review with defined roles and metrics.
Why: walkthrough: Author-led informal review of a work product.
19. What is the purpose of traceability in Concepts?
- A. Developer activity of locating and fixing defect causes.
- B. Testing that executes the software.
- C. Documents from which test cases are derived.
- D. Linking requirements to tests and defects.correct
Why: traceability: Linking requirements to tests and defects.
20. What is the purpose of test basis in Concepts?
- A. Human mistake → flaw in artifact → observable wrong behavior.
- B. Documents from which test cases are derived.correct
- C. Developer activity of locating and fixing defect causes.
- D. Formal, moderated review with defined roles and metrics.
Why: test basis: Documents from which test cases are derived.