ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 191:

  Which of the following statements best describes the way in which decision coverage is measured?

  A. Measured as the number of statements executed by the tests, divided by the total number of executable statements in the code.
  B. Measured as the number of lines of code executed by the tests, divided by the total number of lines of code in the test object.
  C. Measured as the number of decision outcomes executed by the tests, divided by the total number of decision outcomes in the test object.
  D. It is not possible to accurately measure decision coverage.
  C. Measured as the number of decision outcomes executed by the tests, divided by the total number of decision outcomes in the test object.

  ---

  Explanation

  Decision coverage, also known as branch coverage, is measured as the number of decision outcomes executed by the tests divided by the total number of decision outcomes in the test object. It ensures that every possible branch (true/false) decision in the code has been executed at least once.

  ISTQB CTFL Syllabus V4.0, Section 4.3.2

• Question 192:

  A typical objective of testing is to ensure that:

  A. testing is used to drive the development of a software
  B. a software has been tested using a combination of test techniques
  C. there are no defects in a software that is about to be released
  D. a software has been properly covered
  B. a software has been tested using a combination of test techniques

  ---

  Explanation

  This answer is correct because a typical objective of testing is to ensure that a software has been tested using a combination of test techniques, such as black-box, white-box, or experience-based techniques, that are appropriate for the test objectives, test levels, and test types. Testing using a combination of test techniques can increase the effectiveness and efficiency of testing, as different techniques can target different aspects of the software quality, such as functionality, usability, performance, security, reliability, etc. Testing using a combination of test techniques can also reduce the risk of missing defects that could be detected by one technique but not by another.

  References: ISTQB Foundation Level Syllabus v4.0, Section 2.3.1.1, Section 2.3.2

• Question 193:

  The following state diagram is given as basis for state transition testing and contains only valid transitions:

  

  Explanation of the state diagram: States are depicted as nodes. The initial state is I, the final state is

  F. A state transition is depicted as a directed arrow with the initiating event as a label, e. g. from I to S1 with event a, and is also written as a

  triple (I,a,S1). Note: A test case is a sequence of events that initiates the corresponding sequence of state transitions.

  The state diagram contains the following 7 state transitions:

  (I, a, S1)

  (S1, a, S2), (S1, b, S3), (S1, c, F)

  (S2, a, S3)

  (S3, a, S2), (S3, b, F)

  What is the minimum number of test cases to achieve 100% coverage of all valid state transitions in the diagram?

  A. 2
  B. 3
  C. 4
  D. 8
  C. 4

  ---

  Explanation

• Question 194:

  Software was found lo take much more time than the stated requirement of less than one second to save a file. Upon investigation it was found that there was an unnecessary check inside a loop which was slowing down the file-save operation. The software not being able to meet the desired response time is an example of

  A. It is not a defect
  B. Defect
  C. Error
  D. Failure
  D. Failure

  ---

  Explanation

  A failure is an event in which a component or system does not perform a required function within specified limits. A failure is observable by the software users or other stakeholders. A failure is caused by one or more defects in the software. In this case, the software not being able to meet the desired response time is an example of a failure, as it deviates from the stated requirement and affects the user experience. It is not a defect, which is a flaw in the software that causes the failure. It is not an error, which is a human action that produces an incorrect result. It is not a non-defect, as it clearly violates a specified requirement. Verified

  References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus Springer], Chapter 1, page 4.

• Question 195:

  Which of the following are valid testing principles?

  I) Exhaustive testing is in general impossible.

  II) Exhaustive testing should be executed for code intended to be reused.

  III) Testing may guarantee that a program is correct.

  IV) Testing cannot guarantee that a program is correct.

  V) Defects cluster together in certain areas of the product.

  A. I, IV, V
  B. II, Iv
  C. I, V
  D. I, Ill
  A. I, IV, V

  ---

  Explanation

  Statements I, IV and V are valid testing principles according to the ISTQB syllabus. Statement I states that exhaustive testing is in general impossible, because it would require testing all possible inputs, outputs and combinations of states, which is usually impractical or impossible. Statement IV states that testing cannot guarantee that a program is correct, because testing can only show the presence of defects, not their absence. Statement V states that defects cluster together in certain areas of the product, which means that some modules or functions are more likely to contain defects than others. Statements II and III are invalid testing principles. Statement II states that exhaustive testing should be executed for code intended to be reused, which contradicts statement I. Statement III states that testing may guarantee that a program is correct, which contradicts statement IV. Verified

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, pages 4-5.

• Question 196:

  Which of the following best describes the way in which statement coverage is measured?

  A. Measured as the number of decision outcomes executed by the tests, divided by the total number of decision outcomes in the test object.
  B. It is not possible to accurately measure statement coverage.
  C. Measured as the number of statements executed by the tests, divided by the total number of executable statements in the code.
  D. Measured as the number of lines of code executed by the test, divided by the total number of lines of code in the test object.
  C. Measured as the number of statements executed by the tests, divided by the total number of executable statements in the code.

  ---

  Explanation

  Statement coverage is a metric used in white-box testing that measures the percentage of executable statements in the code that have been executed by the test cases. It is calculated as the number of statements executed by the tests divided by the total number of executable statements in the code, providing an indication of how much of the code has been tested.

• Question 197:

  Which test level primarily verifies that system components interact correctly?

  A. Component testing
  B. Integration testing
  C. System testing
  D. Acceptance testing
  B. Integration testing

  ---

  Explanation

  Integration testing checks interfaces and data flow between components.

• Question 198:

  Which of the following is an example of tasks most associated with the test design activity?

  A. The project manager updates the project schedule as key test tasks are completed
  B. Test data, derived from production data, is loaded into the test environment
  C. Every day. the tester notes the status of his/her test cases in preparation for daily reports
  D. The identification of test execution and test automation tools
  D. The identification of test execution and test automation tools

  ---

  Explanation

  Test design is one of the fundamental activities in software testing, focusing on how tests will be structured and what strategies will be employed. As per the ISTQB syllabus, identifying appropriate test execution and automation tools is a task closely associated with test design activities because it directly influences how tests will be conducted, managed, and executed efficiently. This activity involves deciding on the tools that will best support the testing goals and requirements.

  References:ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 4.4 "Test Design Techniques".

• Question 199:

  Which type of software development product can undergo static testing?

  A. Any software development product can undergo static testing, including requirements specifications, design specifications and code.
  B. Static tests should be performed on the installation and user guide documents as these documents are used by the end user.
  C. Static testing is done only on the code as part of the "code review" sessions Other documents are reviewed, but not by static testing.
  D. Static testing is done only on the requirements You need to execute the software in order to find defects in the code.
  A. Any software development product can undergo static testing, including requirements specifications, design specifications and code.

  ---

  Explanation

  Static testing is a form of testing that does not involve executing the software, but rather analyzing it for defects, errors, or violations of standards. Static testing can be applied to any software development product, including requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. Static testing can be done by using various techniques such as reviews, inspections, walkthroughs, checklists, static analysis tools, etc. Verified

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 7.

• Question 200:

  Which of the following statements about the shift-left approach is FALSE?

  A. The shift-left approach can only be implemented with test automation
  B. The shift-left approach in testing is compatible with DevOps practices.
  C. The shift-left approach can involve security vulnerabilities
  D. The shift-left approach can be supported by static analysis tools.
  A. The shift-left approach can only be implemented with test automation

  ---

  Explanation

  In a formal review process, the recorder's role is typically responsible for documenting the findings of the review team, including action items, decisions, and recommendations. This ensures that there is an accurate record of what was discussed and agreed upon, facilitating follow-up and continuous improvement. Therefore, statement C is correct as per the ISTQB CTFL syllabus.