ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 141:

  Which of the following statements best describes the objective of branch testing?

  A. Branch testing is used to verify the functionality of an application on all logical branches without knowledge of its internal workings.
  B. Branch testing is used to check the interactive reachable branches of the user interface of an application.
  C. Branch testing is used to verify the performance of an application on certain branches.
  D. Branch testing is used to execute some or all branches in the code of an application at least once.
  D. Branch testing is used to execute some or all branches in the code of an application at least once.

  ---

  Explanation

• Question 142:

  Which of the following statements regarding the test-first approach (principle of early testing) is true?

  A. An approach where the tests are written only as needed.
  B. An approach where the tests are written after implementation.
  C. An approach where the tests are written during implementation.
  D. An approach where the tests are written before implementation.
  D. An approach where the tests are written before implementation.

  ---

  Explanation

• Question 143:

  Which ONE of the following activities TYPICALLY belongs to the planning phase of the review process?

  A. A separate defect report is created for each identified defect so that corrective actions can be tracked.
  B. Each reviewer conducts an individual review to identify anomalies, recommendations, and questions.
  C. The purpose and scope of the review are defined, as well as the work product to be reviewed and the exit criteria.
  D. The reviewers analyze and discuss the anomalies found during the review in a joint meeting.
  C. The purpose and scope of the review are defined, as well as the work product to be reviewed and the exit criteria.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:

  The planning phase of the review process (C) includes defining the review's purpose, scope, and exit criteria to ensure alignment. Option A is part of the defect management phase, B happens during individual preparation, and D takes place in the review meeting.

  ISTQB CTFL v4.0 Syllabus, Section 3.2.2 ?Review Process

• Question 144:

  Which test approach will best fit a new project, with little documentation and high probability for bugs?

  A. Exploratory testing
  B. Requirements based testing
  C. Metric based approach
  D. Regression testing
  A. Exploratory testing

  ---

  Explanation

  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 is suitable for a new project with little documentation and high probability for bugs, as it can help uncover unknown requirements, assumptions and risks. Exploratory testing is not requirements based testing, which is an approach to testing that derives test cases from documented requirements or specifications. Requirements based testing is not feasible for a new project with little documentation, as it requires clear and complete requirements to be available. Exploratory testing is not metric based approach, which is an approach to testing that uses quantitative measures to monitor and control the testing process and evaluate the quality of the software product. Metric based approach is not effective for a new project with high probability for bugs, as it may not capture all aspects of quality and may lead to false confidence or unrealistic expectations. Exploratory testing is not regression testing, which is an approach to testing that verifies that previously tested software still performs correctly after changes. Regression testing is not relevant for a new project with no previous versions or baselines. Verified

  References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 5, page 47-48.

• Question 145:

  A test manager has started a cycle of testing for an e-commerce application. The reason for testing is the change in the protocol for connecting to the payment gateway because of new regulations. Which of the following correctly names this type of testing?

  A. Beta testing
  B. Maintenance testing
  C. System integration testing
  D. Retirement testing
  B. Maintenance testing

  ---

  Explanation

• Question 146:

  Which ONE of the following options MOST ACCURATELY describes branch testing?

  A. In branch testing, the coverage items are executable statements. The aim is to design test cases that exercise statements in the code until an acceptable level of coverage is achieved, expressed as a percentage.
  B. In branch testing, the coverage items are control flow transfers between decisions, and the aim is to design test cases to exercise flow transfers in the code until an acceptable level of coverage is achieved. Coverage is measured as the number of branches exercised by the test cases divided by the total number of branches expressed as a percentage.
  C. In branch testing, the coverage items are branches, and the aim is to design test cases to exercise branches in the code until an acceptable level of coverage is achieved. Coverage is measured as the number of branches exercised by the test cases divided by the total number of branches expressed as a percentage.
  D. In branch testing, the coverage items are executable decisions. The aim is to design test cases that exercise statements in the code until an acceptable level of coverage is achieved. Coverage is expressed as a percentage.
  C. In branch testing, the coverage items are branches, and the aim is to design test cases to exercise branches in the code until an acceptable level of coverage is achieved. Coverage is measured as the number of branches exercised by the test cases divided by the total number of branches expressed as a percentage.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:

  Branch testing is a structural testing technique that ensures each branch (decision point) in the control flow is executed at least once. The goal is to measure branch coverage , which is the number of branches exercised divided by the total number of branches.

  (A)

  describes statement testing, not branch testing.

  (B)

  and (D) introduce confusion between decisions and statements, whereas branch testing focuses on control flow branches.

  In simple terms, branch testing checks that all possible decision outcomes (true/false) are executed , whereas statement testing only ensures that each line of code is executed.

  ISTQB CTFL v4.0 Syllabus, Section 4.3.2 ?Branch Testing

• Question 147:

  A program is used to control a manufacturing line (turn machines on and off. start and stop conveyer belts, add raw materials to the flow. etc.). Not all actions are possible at all times. For example, there are certain manufacturing stages that cannot be stopped - unless there is an emergency. A tester attempts to evaluate if all such cases (where a specific action is not allowed) are covered by the tests.

  Which coverage metric will provide the needed information for this analysis?

  A. Code coverage
  B. Data flow coverage
  C. Statement coverage
  D. Branch Coverage
  D. Branch Coverage

  ---

  Explanation

  Branch coverage is a type of structural coverage metric that measures the percentage of branches or decision outcomes that are executed by the test cases. A branch is a point in the code where the control flow can take two or more alternative paths based on a condition. For example, an if-else statement is a branch that can execute either the if-block or the else-block depending on the evaluation of the condition. Branch coverage ensures that each branch is taken at least once by the test cases, and thus reveals the behavior of the software under different scenarios. Branch coverage is also known as decision coverage or all-edges coverage.

  Branch coverage is suitable for testing the cases where a specific action is not allowed, because it can verify that the test cases cover all the possible outcomes of the conditions that determine the action. For example, if the program has a condition that checks if the manufacturing stage can be stopped, then branch coverage can ensure that the test cases cover both the cases where the stage can be stopped and where it cannot be stopped. This way, branch coverage can help identify any missing or incorrect branches that may lead to undesired or unsafe actions.

  The other options are not correct because they are not suitable for testing the cases where a specific action is not allowed. Code coverage is a general term that encompasses various types of coverage metrics, such as statement coverage, branch coverage, data flow coverage, etc. Code coverage does not specify which type of coverage metric is used for the analysis. Data flow coverage is a type of structural coverage metric that measures the percentage of data flow paths that are executed by the test cases. A data flow path is a sequence of statements that define, use, or kill a variable. Data flow coverage is useful for testing the correctness and completeness of the data manipulation in the software, but not for testing the conditions that determine the actions. Statement coverage is a type of structural coverage metric that measures the percentage of statements or lines of code that are executed by the test cases. Statement coverage ensures that each statement is executed at least once by the test cases, but it does not reveal the behavior of the software under different scenarios. Statement coverage is a weaker criterion than branch coverage, because it does not account for the branches or decision outcomes in the code.

  References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54.

• Question 148:

  Which of the following is an advantage of the whole team approach?

  A. It helps avoid the risk of tasks associated with a user story not moving through the Agile task board at an acceptable rate during an iteration.
  B. It helps team members understand the current status of an iteration by visualising the amount of work left to do compared to the time allotted for the iteration
  C. It helps the whole team be more effective in test case design by requiring all team members to master all types of test techniques.
  D. It helps team members develop better relationships with each other and make their collaboration more effective for the benefit of the project.
  D. It helps team members develop better relationships with each other and make their collaboration more effective for the benefit of the project.

  ---

  Explanation

  The whole team approach, often advocated in Agile methodologies, emphasizes collaboration and collective responsibility among all team members. This approach enhances the relationships within the team and improves overall collaboration, which in turn benefits the project's success. According to the ISTQB CTFL Syllabus v4.0, the whole team approach fosters better communication and cooperation, leading to more effective problem-solving and higher-quality outcomes.

• Question 149:

  Which ONE of the following is a CORRECT example of the purpose of a test plan?

  A. A test lead decides to write a detailed test plan so that in future, in case of project failure responsibilities could be assigned to the right person
  B. A test manager should always create a very simple test plan because the purpose of test plan is to ensure that there is documentation for the purpose of audits.
  C. A test plan is a good document to have for the agile projects because it helps the test manager assign tasks to different people
  D. A test manager decides to create a one page test plan for an agile project for communicating the broad activities and explaining why detailed test cases will not be written as mandated by the test policy.
  D. A test manager decides to create a one page test plan for an agile project for communicating the broad activities and explaining why detailed test cases will not be written as mandated by the test policy.

  ---

  Explanation

• Question 150:

  Select the roles required in a formal review:

  A. Author, Management, Facilitator, Review Leader, Reviewers, Scribe
  B. Author, Tester. Facilitator. Review Leader. Reviewers. Scribe
  C. Author, Business analyst. Facilitator, Review Leader. Reviewers. Scribe
  D. Author. Developer, Facilitator. Review Leader. Reviewers. Scribe
  A. Author, Management, Facilitator, Review Leader, Reviewers, Scribe

  ---

  Explanation

  In a formal review, the roles involved typically include the author, management, facilitator (also known as moderator), review leader, reviewers, and scribe. Each role has specific responsibilities to ensure the effectiveness and efficiency of the

  review process:

  The author creates and refines the work product being reviewed.

  Management allocates resources and supports the review process.

  The facilitator manages the review meeting, ensuring it proceeds smoothly.

  The review leader plans the review and ensures it meets its objectives.

  Reviewers examine the work product to identify defects.

  The scribe records issues raised during the review meeting.