ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 221:

  Consider an estimation session in which a six-member Agile team (Memb1..... Memb6) uses the planning poker technique to estimate a user story (in story points). The team members will use a set of cards with the following values: 1,2, 3,5, 8,13,21. Below is the outcome of the first round of estimation for this session:

  

  Which of the following answers BEST describes how the estimation session should proceed?

  A. The final estimate of the user story in story points is determined by applying the three-point estimation technique with the following input values most optimistic estimate - 1, most likely estimate - 3, and most pessimistic estimate - 21
  B. Further estimation rounds should be performed until all team members will pick the card having the same value: this value will represent the final estimate of the user story in story points.
  C. The final estimate of the user story in story points is determined by calculating the average value between the most optimistic estimate of 21 story points (Memb4> and the most pessimistic estimate of 1 story point (Memb6)
  D. Memb6 and Memb4 which have produced the most pessimistic and the most optimistic estimates respectively, should explain the reasons of their choices to stimulate a discussion between all members before proceeding to another estimation round
  D. Memb6 and Memb4 which have produced the most pessimistic and the most optimistic estimates respectively, should explain the reasons of their choices to stimulate a discussion between all members before proceeding to another estimation round

  ---

  Explanation

  In Agile teams using the planning poker technique for estimating user stories, it is common practice to have further discussions and rounds of estimation if there is a significant discrepancy in the initial estimates. This helps in reaching a consensus and ensures that all team members understand the complexity and requirements of the user story. According to the ISTQB CTFL syllabus, planning poker involves discussions to clarify differences in estimates, especially when there is a wide range of values selected. By having Memb6 and Memb4, who provided the most pessimistic and optimistic estimates, explain their reasoning, it fosters a deeper understanding and encourages the team to converge towards a more accurate and agreed-upon estimate.

  References: ISTQB CTFL Syllabus, Section on Agile methodologies and estimation techniques.

• Question 222:

  Which ONE of the following statements about state transition testing is correct?

  A. The state transition diagram explicitly shows all invalid transitions.
  B. The size of the state table depends on the number of possible transitions between the states
  C. Usually it is not possible to create tests to cover ell transitions and all stales
  D. All transitions between states are explicitly shown in the state table.
  D. All transitions between states are explicitly shown in the state table.

  ---

  Explanation

  State transition testing is a black-box testing technique used to analyze the behavior of a system by examining the transitions between different states in response to events. In state transition testing, a state table or diagram is used to represent the states of a system and the transitions between these states triggered by events.

  Option D is correct because in state transition testing, all transitions between states should be explicitly shown in the state table. This includes valid transitions that the system is expected to make under normal operation and, where relevant, invalid transitions that should be tested to ensure the system handles unexpected or erroneous inputs gracefully. The state table provides a comprehensive view of how the system should behave, making it possible to create tests that cover all defined transitions.

• Question 223:

  What type of testing measures its effectiveness by tracking which lines of code were executed by the tests?

  A. Acceptance testing
  B. Structural testing
  C. Integration testing
  D. Exploratory testing
  B. Structural testing

  ---

  Explanation

  Structural testing is a type of testing that measures its effectiveness by tracking which lines of code were executed by the tests. Structural testing, also known as white-box testing or glass-box testing, is based on the internal structure, design, or implementation of the software. Structural testing aims to verify that the software meets the specified quality attributes, such as performance, security, reliability, or maintainability, by exercising the code paths, branches, statements, conditions, or data flows. Structural testing uses various coverage metrics, such as function coverage, line coverage, branch coverage, or statement coverage, to determine how much of the code has been tested and to identify any untested or unreachable parts of the code. Structural testing can be applied at any level of testing, such as unit testing, integration testing, system testing, or acceptance testing, but it is more commonly used at lower levels, where the testers have access to the source code. The other options are not correct because they are not types of testing that measure their effectiveness by tracking which lines of code were executed by the tests. Acceptance testing is a type of testing that verifies that the software meets the acceptance criteria and the user requirements. Acceptance testing is usually performed by the end-users or customers, who may not have access to the source code or the technical details of the software. Acceptance testing is more concerned with the functionality, usability, or suitability of the software, rather than its internal structure or implementation. Integration testing is a type of testing that verifies that the software components or subsystems work together as expected. Integration testing is usually performed by the developers or testers, who may use both structural and functional testing techniques to check the interfaces, interactions, or dependencies between the components or subsystems. Integration testing is more concerned with the integration logic, data flow, or communication of the software, rather than its individual lines of code. Exploratory testing is a type of testing that involves simultaneous learning, test design, and test execution. Exploratory testing is usually performed by the testers, who use their creativity, intuition, or experience to explore the software and discover any defects, risks, or opportunities for improvement. Exploratory testing is more concerned with the behavior, quality, or value of the software, rather than its internal structure or implementation.

  References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54; Chapter 1: Fundamentals of Testing, Section 1.4: Testing Throughout the Software Development Lifecycle, Pages 11-13; Chapter 3: Static Testing, Section 3.4: Exploratory Testing, Pages 40-41.

• Question 224:

  Testing Quadrants, as a model, is effective in aligning stakeholders within Agile teams.

  Which of the following examples demonstrates this?

  A. Using Testing Quadrants, the test manager is able to measure and communicate test coverage to all stakeholders.
  B. Using Testing Quadrants, the test manager is able to communicate potential product risk to all stakeholders.
  C. Using Testing Quadrant, the test manager is able to prioritize defects by linking these to a specific type of test.
  D. Using Testing Quadrants, the test manager is able to differentiate and describe the types of tests to all stakeholders.
  D. Using Testing Quadrants, the test manager is able to differentiate and describe the types of tests to all stakeholders.

  ---

  Explanation

  The Testing Quadrants model helps Agile teams by categorizing different types of tests and their purposes. This differentiation helps test managers explain the testing strategy to all stakeholders, ensuring everyone understands the scope and objectives of each test type. This model aids in planning, executing, and tracking testing activities across different quadrants, making it easier to align with stakeholders' expectations and project goals.

  ISTQB CTFL Syllabus V4.0, Section 5.1.7

• Question 225:

  Which TWO of the following are benefits of continuous integration? Select the correct answer:

  I- Allows earlier detection and easier root cause analysis of integration problems and conflicting changes.

  II- Removes the need for manual test analysis, design and execution.

  Hi- Removes the dependency on automated regression packs when integrating larger systems, or components.

  iv- Gives the development team regular feedback on whether the code is working.

  A. i and iv
  B. i and ii
  C. i and iii
  D. iii and iv
  A. i and iv

  ---

  Explanation

  The benefits of continuous integration include: i. Allows earlier detection and easier root cause analysis of integration problems and conflicting changes. iv. Gives the development team regular feedback on whether the code is working. These benefits help in maintaining the stability and quality of the codebase by integrating and testing changes frequently and providing quick feedback to developers.

• Question 226:

  The following decision table is used to assist a doctor in determining the drug therapy to prescribe for a patient (aged 6 to 65 years) diagnosed with acute sinusitis. The table consists of three Boolean conditions and six actions

  Based only on the given information, which of the following statements is TRUE?

  A. Column 7 represents an impossible situation and thus can be deleted
  B. Columns 1 and 3 can be merged into a single column
  C. Columns 2, 4, 6 and 8 can be merged into a single column
  D. Columns 5 and 7 can be merged into a single column
  B. Columns 1 and 3 can be merged into a single column

  ---

  Explanation

  Decision tables are used to model complex decision logic by considering different combinations of conditions and actions. Based on the given decision table for prescribing drug therapy:

  Column 1 and Column 3 both result in the same actions (prescribing Amoxicillin).

  These columns can be merged because the actions taken do not depend on whether the patient is taking anticoagulant therapy (both are 'T' for this condition).

  Thus, combining these columns simplifies the decision table without losing any information.

  ISTQB CTFL Syllabus V4.0, Chapter 4.2.3, Decision Table Testing.

• Question 227:

  A company wants to reward each of its salespeople with an annual bonus that represents the sum of all the bonuses accumulated for every single sale made by that salesperson. The bonus for a single sale can take on the following four values: 3%, 5%, 7% and 10% (the percentage refers to the amount of the single sale). These values are determined on the basis of the type of customer (classified as "Basic" or "Premium") to which such sale was made, and on the amount of such sale classified into the following three groups G1, G2 and G3:

  1.[G1]: less than 300 euros

  2.[G2]: between 300 and 2000 euros

  3.[G3]: greater than 2000 euros

  Which of the following is the minimum number of test cases needed to cover the full decision table associated with this scenario?

  A. 12
  B. 6
  C. 4
  D. 3
  B. 6

  ---

  Explanation

  The minimum number of test cases needed to cover the full decision table associated with this scenario is 6. This is because the decision table has 4 conditions (type of customer and amount of sale) and 4 actions (bonus percentage). The conditions have 2 possible values each (Basic or Premium, and G1, G2 or G3), so the total number of combinations is 2 x 2 x 2 x 2 = 16. However, not all combinations are valid, as some of them are contradictory or impossible. For example, a sale cannot be both less than 300 euros and greater than 2000 euros at the same time. Therefore, we need to eliminate the invalid combinations and keep only the valid ones. The valid combinations are:

  Type of customer Amount of sale Bonus percentage Basic G1 3% Basic G2 5% Basic G3 7% Premium G1 5% Premium G2

  7%

  Premium

  G3

  10%

  These 6 combinations cover all the possible values of the conditions and actions, and they are the minimum number of test cases needed to cover the full decision table.

• Question 228:

  Which of the following statements about branch coverage is true?

  A. The minimum number of test cases needed to achieve full branch coverage, is usually lower than that needed to achieve full statement coverage
  B. If full branch coverage has been achieved, then all unconditional branches within the code have surely been exercised
  C. If full branch coverage has been achieved, then all combinations of conditions in a decision table have surely been exercised
  D. Exercising at least one of the decision outcomes for all decisions within the code, ensures achieving full branch coverage
  D. Exercising at least one of the decision outcomes for all decisions within the code, ensures achieving full branch coverage

  ---

  Explanation

  Exercising at least one of the decision outcomes for all decisions within the code, ensures achieving full branch coverage, which is a test coverage criterion that requires that all branches in the control flow of the code are executed at least once by the test cases. A branch is a basic block of code that has a single entry point and a single exit point, and a decision is a point in the code where the control flow can take more than one direction, such as an if-then-else statement, a switch-case statement, a loop statement, etc. The decision outcomes are the possible paths that can be taken from a decision, such as the then branch or the else branch, the case branch or the default branch, the loop body or the loop exit, etc. The other statements are false, because:

  The minimum number of test cases needed to achieve full branch coverage, is usually higher than that needed to achieve full statement coverage, which is a test coverage criterion that requires that all executable statements in the code are executed at least once by the test cases. This is because branch coverage is a stronger criterion than statement coverage, as it implies statement coverage, but not vice versa. For example, a single test case can achieve full statement coverage for an if-then-else statement, but two test cases are needed to achieve full branch coverage, as both the then branch and the else branch need to be exercised. If full branch coverage has been achieved, then all unconditional branches within the code have not necessarily been exercised, as unconditional branches are branches that do not depend on any decision, and are always executed, such as a goto statement, a break statement, a return statement, etc. Unconditional branches are not part of the branch coverage criterion, as they do not represent different paths in the control flow of the code. However, they are part of the statement coverage criterion, as they are executable statements in the code. If full branch coverage has been achieved, then all combinations of conditions in a decision table have not necessarily been exercised, as a decision table is a test design technique that represents the logical relationships between multiple conditions and their corresponding actions, in a tabular format. A decision table can have more combinations of conditions than the number of decision outcomes in the code, as each condition can have two or more possible values, such as true or false, yes or no, etc. For example, a decision table with four conditions can have 16 combinations of conditions, but the corresponding code may have only two decision outcomes, such as pass or fail. To exercise all combinations of conditions in a decision table, a stronger test coverage criterion is needed, such as condition combination coverage, which requires that all possible combinations of condition outcomes in the code are executed at least once by the test cases.

  References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents: ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.3.1, Test Coverage Criteria Based on the Structure of the Software ISTQB Glossary of Testing Terms v4.0, Branch Coverage, Statement Coverage, Branch, Decision, Decision Outcome, Unconditional Branch, Decision Table, Condition Combination Coverage

• Question 229:

  The following chart represents metrics related to testing of a project that was competed. Indicate what is represented by tie lines A, B and the axes X.Y

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  D. Option D

  ---

  Explanation

  Option D correctly explains what is represented by the lines A, B and the axes X, Y in a testing metrics chart.

  According to option D: X-axis represents Time Y-axis represents Count Line A represents Number of open bugs Line B represents Total number of executed tests This information is essential in understanding and analyzing the testing metrics of a completed project. ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Section 2.5.1, Page 35.

• Question 230:

  As the last stage of a test cycle of an embedded device, you are performing exploratory testing. You observed that some character. (A, X and Z) sent via a serial port to the device do not get registered on the device whereas they should be. You suspect that this could be due to a wrong configuration of the "bit parity" parameter.

  Which of the following items of an incident report would you be UNABLE to write down based on this information?

  A. Expected result
  B. Test case identifier
  C. Test setup details
  D. Actual result
  B. Test case identifier

  ---

  Explanation

  An incident report is a document that records the details of an incident. An incident report typically contains the following items:

  Identifier: A unique identifier for the incident report Summary: A concise summary of the incident Description: A detailed description of the incident, including the steps to reproduce it, the expected and actual results, and any relevant screenshots or logs Severity: The degree of impact that the incident has on the system Priority: The level of urgency for resolving the incident Status: The current state of the incident, such as new, open, resolved, closed, etc. Resolution: The action taken to resolve the incident, such as fix, workaround, reject, etc. Based on the information given in the question, the tester would be able to write down all of these items except for the test case identifier. A test case identifier is a unique identifier for a test case that is used to link it to other test artifacts, such as test plans, test scripts, test results or incident reports. However, since the tester is performing exploratory testing, there is no predefined test case that can be associated with the incident. Exploratory testing is an approach to testing that emphasizes learning, test design and test execution at the same time. Exploratory testing relies on the tester's skills, creativity and intuition to explore the software under test and discover defects. Exploratory testing does not use formal test cases or scripts, but rather uses test charters or missions that guide the tester's actions and objectives.

  Verified

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page 32-33; Chapter 5, page 47-48.