ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 281:

  You are working in an agile team on the creation of software for use in robotic assistance systems that support industrial manufacturing processes. You are currently in the effort estimation phase using planning poker. In the current sprint, three user stories are to be implemented:

  A: The assistance system is to have a customizable layout. For this purpose, the user should be able to choose between 3 combinations of font size and background color at startup.

  B: In the initialization phase, the assistance system should validate the inputs of the 10 customer specific and process specific parameters against a list of 5 consistency rules and display the result to the user.

  C: The assistance system currently supports the manufacturing process with 2 robot gripper arms, this shall be extended to 5 gripper arms. In addition, the system shall perform a pre-calculation of the movements of all gripper arms in real time and automatically stop the system in case of a calculated collision of the gripper arms.

  You are now asked to estimate the test effort for each of these user stories by using planning poker. The following value rules apply for the test effort estimation:

  3 - low (<= 10 test cases)

  8 - medium (> 10 and <= 20 test cases)

  13 - high (> 20 and <= 50 test cases)

  21 - very high (> 50 and <= 100 test cases)

  34 - too complex (number of test cases cannot be estimated from information)

  For each of the three user stories, which planning poker value makes the most sense when estimating the test effort?

  A. A:3; B:21; C:8;
  B. A:21; B:13; C:13;
  C. A:3; B:13; C:34;
  D. A:13; B:13; C:13;
  A. A:3; B:21; C:8;

  ---

  Explanation

• Question 282:

  4 equivalence classes are given for integer values:

  0 < x <100 100<= x <= 200 200 < x < 500 x >= 500

  Which of the following options represent correct set of data for valid equivalence class partitions?

  A. 50; 100; 200. 1000
  B. 0. 1.99, 100.200,201.499, 500;
  C. 0.50; 100; 150.200.350.500;
  D. 50; 100; 250; 1000
  C. 0.50; 100; 150.200.350.500;

  ---

  Explanation

  The correct set of data for valid equivalence class partitions should include one value from each equivalence class, and no value from outside the range.

  Option C satisfies this condition, as it has one value from each of the four equivalence classes (50, 100, 250, 500).

  Option A has two values from the same equivalence class (100 and 200), option B has values outside the range (0 and 0.99), and option D has two values from the same equivalence class (1000 and 500).

  Verified

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

• Question 283:

  Which ONE of the following work products TYPICALLY belongs to test execution?

  A. Test logs that document the results of test execution.
  B. Automated test scripts used for test execution.
  C. A test plan that describes the test strategy and test objectives.
  D. A list of test conditions prioritized during test analysis.
  A. Test logs that document the results of test execution.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:

  Test execution involves running test cases and documenting results. Test logs (A) provide evidence of executed tests, failures, and actual outcomes. Automated test scripts (B) are part of test implementation, test plans (C) belong to test planning, and test conditions (D) are identified during test analysis.

  ISTQB CTFL v4.0 Syllabus, Section 1.4.1 ?Test Execution

• Question 284:

  You work as a test manager for a supplier of PC games which can be purchased and downloaded via an online store. A tester from your team recorded the following failure caused by a defect:

  1.Issue ID: DEF00223167

  2.Title: Saving after shopping in online shop fails

  3.Date: 2023-04-18

  4.Tester: Sabine Meier

  5.Description: "Saving the game immediately after purchasing it in the online store fails. As a result, the purchase is paid for, but the goods are not delivered."

  6.Attached data: "log.txt", "screen1.bmp", "screen2.bmp"

  During the review of the defect report, you notice that at least one important piece of information is missing for defining how to deal with the defect. Which one?

  A. Severity of the defect
  B. Name of the developer who most likely caused the defect
  C. Tracking the quality of the work product
  D. Ideas for test process improvement
  A. Severity of the defect

  ---

  Explanation

• Question 285:

  Which sequence of state transition stated in the answer choices is correct in accordance with the following figure depicting me life-cycle of a defect?

  

  A. S0->S1->S2->S3->S4
  B. S0->S1->S2->S3->S5^>S1
  C. S0->S1->S2->S3->S5->S1->S2->S3
  D. S0->S1->S2->S3->S5->S3->S4
  C. S0->S1->S2->S3->S5->S1->S2->S3

  ---

  Explanation

  The figure depicts the life-cycle of a defect using state transition testing. State transition testing is a technique that models how a system transitions from one state to another depending on events or conditions. The figure shows six states (S0

  to S5) and seven transitions (T0 to T6). The correct sequence of state transitions that follows the figure is S0->S1->S2->S3->S5->S1->S2->S3. This sequence represents the following scenario:

  S0: The defect is not yet detected (initial state).

  T0: The defect is detected by testing (event).

  S1: The defect is reported and registered (state).

  T1: The defect is assigned to a developer for fixing (event).

  S2: The defect is being fixed by the developer (state).

  T2: The developer fixes the defect and delivers a new version (event).

  S3: The defect is verified by testing (state).

  T5: The testing fails to confirm that the defect is fixed (event).

  S5: The defect is rejected by testing (state).

  T6: The defect is reassigned to a developer for fixing (event).

  S1: The defect is reported and registered (state).

  T1: The defect is assigned to a developer for fixing (event).

  S2: The defect is being fixed by the developer (state).

  T2: The developer fixes the defect and delivers a new version (event).

  S3: The defect is verified by testing (state). The other sequences are incorrect, as they do not follow the transitions shown in the figure.

  Verified

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

• Question 286:

  Which of the following correctly represents a test first approach?

  A. Code is refactored first then tests are written and run
  B. Application behaviour is written in Given/When/then format and tests are then written and run
  C. Tests are derived from acceptance criteria and run to check that the code passes these tests
  D. First the tests fail then the code is written to pass the tests and this is iterated
  D. First the tests fail then the code is written to pass the tests and this is iterated

  ---

  Explanation

• Question 287:

  Which of the following activities does NOT belong to a typical technical review?

  A. Pre-meeting preparation by reviewers
  B. Using checklists during the meeting
  C. Inviting end-users to the meeting
  D. Preparation of a review report
  C. Inviting end-users to the meeting

  ---

  Explanation

  Technical reviews are structured meetings that aim to examine various aspects of a product or project to identify any defects or improvements. Options A (Pre-meeting preparation by reviewers), B (Using checklists during the meeting), and D (Preparation of a review report) are typical activities in a technical review process. Inviting end-users to the meeting (C), however, is generally not part of a typical technical review, as these reviews are usually more focused on the technical aspects and are conducted by peers or experts within the development or testing teams rather than end-users.

• Question 288:

  A team's test strategy was to invest equal effort in testing each of a system's modules. After running one test cycle, it turned out that most of the critical bugs were detected in one of the system's modules.

  Which testing principal suggests a change to the current test strategy for the next test cycle?

  A. Pesticide Paradox
  B. Early testing
  C. Absence-of-errors fallacy
  D. Defect clustering
  D. Defect clustering

  ---

  Explanation

  Defect clustering is a testing principle that states that a small number of modules contain most of the defects detected during pre-release testing, or are responsible for most of the operational failures. Defect clustering can be explained by Pareto's principle (also known as the 80-20 rule), which states that approximately 80% of the problems are found in 20% of the modules. Defect clustering suggests a change to the current test strategy for the next test cycle, as it implies that more effort should be allocated to test the modules that have shown high defect density or criticality. Pesticide paradox is another testing principle that states that if the same tests are repeated over and over again, eventually they will no longer find any new defects. Pesticide paradox suggests a change to the current test strategy for the next test cycle, but not based on defect clustering, but rather on test diversity and coverage. Early testing is a testing principle that states that testing activities should start as early as possible in the software development life cycle and should be focused on defined objectives. Early testing does not suggest a change to the current test strategy for the next test cycle, but rather a proactive approach to prevent defects from occurring or propagating. Absence-of-errors fallacy is a testing principle that states that finding and fixing defects does not help if the system built is unusable and does not fulfill the users' needs and expectations. Absence-of-errors fallacy does not suggest a change to the current test strategy for the next test cycle, but rather a focus on quality attributes and user requirements. Verified

  References: A Study Guide to the ISTQB Foundation

  Level 2018 Syllabus - Springer, Chapter 1, page 9-10.

• Question 289:

  Consider the following list of possible benefits of retrospectives (A to D):

  Consider the following list of possible benefits of retrospectives (A to D):

  A: Team bonding and learning

  B: Increased test effectiveness/efficiency

  C: Improved quality of the test basis

  D: Better cooperation between development and testing

  .... and the list of possible characteristics of retrospectives (1 to 4) that enable achieving these benefits:

  1.The possibility of implementing suggestions for process improvement

  2.The opportunity to raise problems and propose points for improvement

  3.The regular review and optimization of the collaboration between team members

  4.The possibility of addressing and solving deficiencies in the extent and quality of the requirements

  Which ONE of the following options presents the BEST mapping between benefits and characteristics from retrospectives?

  A. A1 - B4 - C3 - D2
  B. A2 - B1 - C4 - D3
  C. A4 - B3 - C2 - D1
  D. A3 - B2 - C1 - D4
  B. A2 - B1 - C4 - D3

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:

  Retrospectives provide value by fostering improvement and collaboration. The correct mapping is:

  A2: Team bonding occurs when teams openly discuss issues.

  B1: Test effectiveness increases when process improvements are implemented.

  C4: Test basis improves by addressing requirement deficiencies.

  D3: Cooperation improves through regular review of collaboration.

  ISTQB CTFL v4.0 Syllabus, Section 2.1.6 ?Retrospectives

• Question 290:

  Which of the following statements is true?

  A. Experience-based test techniques rely on the experience of testers to identify the root causes of defects found by black-box test techniques
  B. Some of the most common test basis used by white-box test techniques include user stories, use cases and business processes
  C. Experience-based test techniques are often useful to detect hidden defects that have not been targeted by black-box test techniques
  D. The primary goal of experience-based test techniques is to design test cases that can be easily automated using a GUI-based test automation tool
  C. Experience-based test techniques are often useful to detect hidden defects that have not been targeted by black-box test techniques

  ---

  Explanation

  Experience-based test techniques are test design techniques that rely on the experience, knowledge, intuition, and creativity of the testers to identify and execute test cases that are likely to find defects in the software system. Experience-based test techniques are often useful to detect hidden defects that have not been targeted by black-box test techniques, which are test design techniques that use the external behavior and specifications of the software system as the test basis, without considering its internal structure or implementation. Experience-based test techniques can complement black-box test techniques by covering aspects that are not explicitly specified, such as usability, security, reliability, performance, etc. The other statements are false, because: Experience-based test techniques do not rely on the experience of testers to identify the root causes of defects found by black-box test techniques, but rather to identify the potential sources of defects based on their own insights, heuristics, or exploratory testing. The root causes of defects are usually identified by debugging or root cause analysis, which are activities that involve examining the code or the development process to find and fix the errors that led to the defects. Some of the most common test basis used by white-box test techniques include the source code, the design documents, the architecture diagrams, and the control flow graphs of the software system. White- box test techniques are test design techniques that use the internal structure and implementation of the software system as the test basis, and aim to achieve a certain level of test coverage based on the code elements, such as statements, branches, paths, etc. User stories, use cases, and business processes are examples of test basis used by black-box test techniques, as they describe the functional and non- functional requirements of the software system from the perspective of the users or the stakeholders. The primary goal of experience-based test techniques is not to design test cases that can be easily automated using a GUI-based test automation tool, but rather to design test cases that can reveal defects that are not easily detected by other test techniques, such as boundary value analysis, equivalence partitioning, state transition testing, etc. Test automation is the use of software tools to execute test cases and compare actual results with expected results, without human intervention. Test automation can be applied to different types of test techniques, depending on the test objectives, the test levels, the test tools, and the test resources. However, test automation is not always feasible or beneficial, especially for test cases that require human judgment, creativity, or exploration, such as those designed by experience-based test techniques.

  References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents: ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.1, Black-box Test Design Techniques ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.2, White-box Test Design Techniques ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.3, Experience-based Test Design Techniques ISTQB Glossary of Testing Terms v4.0, Experience-based Test Technique, Black-box Test Technique, White-box Test Technique, Test Basis, Test Coverage, Test Automation