STLC interview questions — Easy
132 easy-level STLC 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
STLC 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 which STLC phase are test cases actually run against the build?
- A. Test Planning.
- B. Test Design.
- C. Requirement Analysis.
- D. Test Execution.correct
Why: Test cases are run during the Test Execution phase and results are logged.
2. In the context of STLC, test summary report is best described as:
- A. Quick verification a build is stable enough for testing.
- B. Document defining scope, approach, resources, and schedule of testing.
- C. Closure document summarizing results and quality.correct
- D. Steps, data, and expected results validating a condition.
Why: test summary report: Closure document summarizing results and quality.
3. Which of the following best describes smoke test entry gate in STLC?
- A. High-level description of functionality to be tested.
- B. Closure document summarizing results and quality.
- C. Input values prepared for executing test cases.
- D. Quick verification a build is stable enough for testing.correct
Why: smoke test entry gate: Quick verification a build is stable enough for testing.
4. Which is the correct high-level order of the Software Testing Life Cycle (STLC)?
- A. Test execution → Requirement analysis → Test design → Closure.
- B. Requirement analysis → Test planning → Test design → Test execution → Closure.correct
- C. Test planning → Test execution → Requirement analysis → Closure.
- D. Test design → Closure → Test planning → Execution.
Why: STLC flows: requirement analysis, test planning, test case design, environment setup, test execution, then test cycle closure.
5. On a release readiness call: Which STLC phase produces the Requirement Traceability Matrix (RTM)?
- A. Defect Retesting.
- B. Test Execution.
- C. Requirement Analysis.correct
- D. Test Closure.
Why: The RTM is created during Requirement Analysis to map requirements to test cases.
6. On a release readiness call: What is the first phase of the Software Testing Life Cycle (STLC)?
- A. Test Closure.
- B. Test Execution.
- C. Requirement Analysis.correct
- D. Environment Setup.
Why: STLC begins with Requirement Analysis where testers study testable requirements.
7. Which of the following best describes test summary report in STLC?
- A. Input values prepared for executing test cases.
- B. Closure document summarizing results and quality.correct
- C. Document defining scope, approach, resources, and schedule of testing.
- D. Quick verification a build is stable enough for testing.
Why: test summary report: Closure document summarizing results and quality.
8. In STLC, what does test summary report do or refer to?
- A. Steps, data, and expected results validating a condition.
- B. Quick verification a build is stable enough for testing.
- C. Closure document summarizing results and quality.correct
- D. Document defining scope, approach, resources, and schedule of testing.
Why: test summary report: Closure document summarizing results and quality.
9. Which of the following best describes test case in STLC?
- A. Steps, data, and expected results validating a condition.correct
- B. High-level description of functionality to be tested.
- C. Document defining scope, approach, resources, and schedule of testing.
- D. Quick verification a build is stable enough for testing.
Why: test case: Steps, data, and expected results validating a condition.
10. What is the purpose of test case in STLC?
- A. Quick verification a build is stable enough for testing.
- B. Input values prepared for executing test cases.
- C. Steps, data, and expected results validating a condition.correct
- D. Document defining scope, approach, resources, and schedule of testing.
Why: test case: Steps, data, and expected results validating a condition.
11. What is the purpose of smoke test entry gate in STLC?
- A. Input values prepared for executing test cases.
- B. Document defining scope, approach, resources, and schedule of testing.
- C. Closure document summarizing results and quality.
- D. Quick verification a build is stable enough for testing.correct
Why: smoke test entry gate: Quick verification a build is stable enough for testing.
12. What is the purpose of test plan in STLC?
- A. Quick verification a build is stable enough for testing.
- B. High-level description of functionality to be tested.
- C. Document defining scope, approach, resources, and schedule of testing.correct
- D. Input values prepared for executing test cases.
Why: test plan: Document defining scope, approach, resources, and schedule of testing.
13. Which of the following best describes test scenario in STLC?
- A. Steps, data, and expected results validating a condition.
- B. Document defining scope, approach, resources, and schedule of testing.
- C. High-level description of functionality to be tested.correct
- D. Quick verification a build is stable enough for testing.
Why: test scenario: High-level description of functionality to be tested.
14. In STLC, what does smoke test entry gate do or refer to?
- A. Steps, data, and expected results validating a condition.
- B. Quick verification a build is stable enough for testing.correct
- C. High-level description of functionality to be tested.
- D. Input values prepared for executing test cases.
Why: smoke test entry gate: Quick verification a build is stable enough for testing.
15. In STLC, what does test case do or refer to?
- A. Input values prepared for executing test cases.
- B. Steps, data, and expected results validating a condition.correct
- C. Document defining scope, approach, resources, and schedule of testing.
- D. Quick verification a build is stable enough for testing.
Why: test case: Steps, data, and expected results validating a condition.
16. In STLC, what does test plan do or refer to?
- A. High-level description of functionality to be tested.
- B. Closure document summarizing results and quality.
- C. Input values prepared for executing test cases.
- D. Document defining scope, approach, resources, and schedule of testing.correct
Why: test plan: Document defining scope, approach, resources, and schedule of testing.
17. Which of the following best describes test plan in STLC?
- A. High-level description of functionality to be tested.
- B. Document defining scope, approach, resources, and schedule of testing.correct
- C. Quick verification a build is stable enough for testing.
- D. Steps, data, and expected results validating a condition.
Why: test plan: Document defining scope, approach, resources, and schedule of testing.
18. In STLC, what does test scenario do or refer to?
- A. Document defining scope, approach, resources, and schedule of testing.
- B. Closure document summarizing results and quality.
- C. High-level description of functionality to be tested.correct
- D. Quick verification a build is stable enough for testing.
Why: test scenario: High-level description of functionality to be tested.
19. What is the purpose of test summary report in STLC?
- A. Steps, data, and expected results validating a condition.
- B. Input values prepared for executing test cases.
- C. Closure document summarizing results and quality.correct
- D. Quick verification a build is stable enough for testing.
Why: test summary report: Closure document summarizing results and quality.
20. What is the purpose of test scenario in STLC?
- A. High-level description of functionality to be tested.correct
- B. Document defining scope, approach, resources, and schedule of testing.
- C. Closure document summarizing results and quality.
- D. Quick verification a build is stable enough for testing.
Why: test scenario: High-level description of functionality to be tested.