ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 211:

  Which of the following work products cannot be examined by static analysis?

  A. Test plans
  B. Source code
  C. Compiled code
  D. Formal models
  A. Test plans

  ---

  Explanation

  Static analysis is the process of examining the work products of a software development or testing activity without executing them. Static analysis can be applied to various types of work products, such as requirements, design, code, test

  cases, etc. However, test plans are not suitable for static analysis, because they are high-level documents that describe the test objectives, scope, strategy, resources, schedule, and risks of a testing project. Test plans are not executable or

  formalized in a way that static analysis tools can analyze them.

  Therefore, option A is the correct answer.ISTQB Certified Tester Foundation Level Syllabus v4.01, Section 2.2.1, page 20; ISTQB Glossary v4.02, page 45.

• Question 212:

  Which of the following BEST describes a benefit of test automation?

  A. More subjective assessment
  B. Reduction in repetitive manual work
  C. Availability of the test automation tool vendor
  D. Negligible effort to maintain the test assets generated by the tool
  B. Reduction in repetitive manual work

  ---

  Explanation

  Test automation provides numerous benefits to software testing, and one of the key advantages is the reduction of repetitive manual work. This benefit is explicitly covered in the ISTQB Foundation Level Syllabus (v4.0).

  Test automation allows testers to automate repetitive tasks such as regression testing, freeing up their time to focus on more complex and exploratory testing. This leads to improved efficiency and helps in avoiding human errors associated

  with repetitive tasks.

  Option A: "More subjective assessment" contradicts the benefit of automation as it focuses on objectivity.

  Option C: "Availability of the test automation tool vendor" is not a direct benefit of test automation, although vendor support can be valuable. Option D: "Negligible effort to maintain the test assets" is misleading as maintaining automated tests

  often requires effort and attention to changes in the system under test.

  Therefore, the correct answer is B (ISTQB not-for-profit association) (ISTQB).

  References:

  Certified Tester Foundation Level v4.0

  ISTQB Foundation Level Syllabus 4.0 (2023)

• Question 213:

  Which statement best describes the key difference between a mindset for test activities and a mindset for development activities?

  A. A tester possesses professional pessimism while a developer is concerned with validating the product
  B. A tester is concerned with finding defects while a developer is interested in designing solutions
  C. A tester is interested in building solutions while a developer is concerned with verifying the product
  D. A tester is concerned with verifying the product while a developer possesses professional pessimism
  B. A tester is concerned with finding defects while a developer is interested in designing solutions

  ---

  Explanation

  The key difference between the mindsets for test activities and development activities lies in the objectives: a tester is primarily concerned with finding defects to ensure product quality, while a developer focuses on designing and building solutions. This distinct focus helps ensure thorough quality checks and balances within the software development life cycle (ISTQB not-for-profit association).

  ISTQB Certified Tester Foundation Level Syllabus v4.0: https://istqb-main-web-prod.s3.amazonaws.com /media/documents/ISTQB_CTFL_Syllabus-v4.0.pdf

• Question 214:

  In which one of the following test techniques are test cases derived from the analysis of the software architecture?

  A. Black-box test techniques.
  B. Experience-based test techniques.
  C. Checklist-based test techniques.
  D. White-box test techniques.
  D. White-box test techniques.

  ---

  Explanation

  White-box test techniques are test design techniques where the test cases are derived from the internal structure of the software, including its architecture, code, and logical flow. These techniques involve the tester having knowledge of the internal workings of the software to create test cases that ensure all possible paths and conditions are tested. This is in contrast to black-box test techniques, which focus on input-output behavior without considering the internal structure.

  ISTQB CTFL Syllabus V4.0, Section 4.3

• Question 215:

  Which of the following statements about test activities that form the overall test process is correct?

  A. Test planning determines what is to be tested based on the test basis.
  B. Test analysis evaluates the test base and the test elements to identify inconsistencies.
  C. Test design develops and prioritizes test procedures and may create automated test scripts.
  D. Test implementation realization answers the question of how to perform the test, and the test procedure compares the results of the test with the expected results.
  B. Test analysis evaluates the test base and the test elements to identify inconsistencies.

  ---

  Explanation

• Question 216:

  Which of the following coverage criteria results in the highest coverage for state transition based test cases?

  A. Can't be determined
  B. Covering all transitions at least once
  C. Covering only start and end states
  D. Covering all states at least once
  B. Covering all transitions at least once

  ---

  Explanation

  Covering all transitions at least once is the highest coverage criterion for state transition based test cases, because it ensures that every possible change of state is tested at least once. This means that all the events that trigger the transitions, as well as the actions and outputs that result from the transitions, are verified. Covering all transitions at least once also implies covering all states at least once, but not vice versa. Therefore, option D is not the highest coverage criterion. Option C is the lowest coverage criterion, because it only tests the initial and final states of the system or component, without checking the intermediate states or transitions. Option A is incorrect, because the coverage criteria for state transition based test cases can be determined and compared based on the number of transitions and states covered.

  References: CTFL 4.0 Syllabus, Section 4.2.3, page 49-50.

• Question 217:

  Which of the following provides the BEST description of statement coverage?

  A. A white-box test technique which covers the decision results which determine the next statement to be executed
  B. A black-box test technique which uses a state table to derive test cases
  C. A white-box test technique which focuses on the percentage of executable statements that has been executed by a test suite
  D. An experience-based test technique in which test cases are based on the tester's knowledge of past failures
  C. A white-box test technique which focuses on the percentage of executable statements that has been executed by a test suite

  ---

  Explanation

  Statement coverage is a white-box test technique which focuses on executing all possible statements in the code at least once during testing. This helps in determining the percentage of executable statements that have been executed by the test suite, aiming to ensure that all parts of the program have been tested at least once (ISTQB Main Web).

  References:ISTQB Certified Tester Foundation Level Syllabus v4.0: ISTQB CTFL Syllabus v4.0 PDF

• Question 218:

  Use Scenario 1 "Happy Tomatoes" (from the previous question).

  When running test case TC_59, the actual result for t = 35 degrees Celsius is OUTPUT = X instead of the expected output.

  Which information should NOT be included in the defect report?

  A. Identification of the test object and test environment
  B. A concise title and a short summary of the defect being reported
  C. Description of the structure of the test team
  D. Expected results and actual results
  C. Description of the structure of the test team

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:

  A defect report should contain relevant details to help developers reproduce and fix the defect efficiently.

  The essential elements include:

  Test object and environment (A) To ensure reproducibility.

  Title and summary (B) For quick identification.

  Expected vs. actual results (D) To describe the discrepancy.

  The structure of the test team (C) is irrelevant for defect tracking and resolution.

  ISTQB CTFL v4.0 Syllabus, Section 5.5 ?Defect Management

• Question 219:

  Match each objective to the correct test level

  Objective:

  A. Verifying whetherthe functionalandnon-functlonalbehaviorsof the system are as designed andspecified.
  B. Verifying whetherthe functionalandnon-functlonalbehaviorsof the interfaces are as designed.
  C. Verifying whetherthe functionalandnon-functionalbehaviorsof the components are as designedand specified.
  D. Establishing confidence in the quality of the systemas a whole. Test Level: 1.Component testing. 2.Integration testing. 3.System testing. 4.Acceptance testing.
  E. A3, B2. C4. D1
  F. A2, B3, Cl, D4
  G. A3. B2. C1. D4
  C. Verifying whetherthe functionalandnon-functionalbehaviorsof the components are as designedand specified.

  ---

  Explanation

  The test levels and their objectives can be matched as follows:

  Verifying whether the functional and non-functional behaviors of the system are as designed and specified (A3: System testing).

  Verifying whether the functional and non-functional behaviors of the interfaces are as designed (B2:Integration testing).

  Verifying whether the functional and non-functional behaviors of the components are as designed and specified (C1: Component testing).

  Establishing confidence in the quality of the system as a whole (D4: Acceptance testing).

• Question 220:

  Which of the following activities is NOT a pan of the fundamental testing process?

  A. Archiving automation code
  B. Test status reporting
  C. Test process improvement
  D. Build release and maintenance
  D. Build release and maintenance

  ---

  Explanation

  The fundamental testing process includes activities that are directly related to the planning, preparation, execution, and evaluation of tests, as well as the closure activities of the testing phase. Option D, "Build release and maintenance," falls outside the scope of the fundamental testing process as it relates more to software development and operations rather than specific testing activities. Options A, "Archiving automation code," B, "Test status reporting," and C, "Test process improvement," are all activities that can be part of or associated with the fundamental testing process. Archiving automation code is part of test closure, test status reporting is part of test monitoring and control, and test process improvement can be an outcome of test closure activities.