ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 301:

  Which of the following is a good testing practice which is applicable INDEPENDENT of the software development lifecycle followed?

  A. Not all development activities should have corresponding test activities
  B. Each test level should have an appropriate test objective
  C. Large amount of redundancy between test levels is good because it prevents bug leakage
  D. Reviews should be done after the work products have been finalized
  B. Each test level should have an appropriate test objective

  ---

  Explanation

• Question 302:

  Can "cost" be regarded as Exit criteria?

  A. Yes. Spending too much money on test ng will result in an unprofitable product, and having cost as an exit criterion helps avoid this
  B. No. The financial value of product quality cannot be estimated, so it is incorrect to use cost as an exit criterion
  C. Yes. Going by cost as an exit criterion constrains the testing project which will hello achieve the desired quality level defined for the project
  D. No The cost of testing cannot be measured effectively, so it is incorrect to use cost as an exit criterion
  A. Yes. Spending too much money on test ng will result in an unprofitable product, and having cost as an exit criterion helps avoid this

  ---

  Explanation

  Cost can be regarded as an exit criterion for testing, because it is a factor that affects the profitability and feasibility of the software product. Testing is an investment that aims to improve the quality and reliability of the software product, but it also consumes resources, such as time, money, and human effort. Therefore, testing should be planned and executed in a way that balances the cost and benefit of testing activities. Having cost as an exit criterion helps to avoid spending too much money on testing, which may result in an unprofitable product or a loss of competitive advantage. Cost can also help to prioritize and focus the testing efforts on the most critical and valuable features and functions of the software product. However, cost should not be the only exit criterion for testing, as it may not reflect the true quality and risk level of the software product. Other exit criteria, such as defect rate, test coverage, user satisfaction, etc., should also be considered and defined in the test plan. The other options are incorrect, because they either deny the importance of cost as an exit criterion, or they make false or unrealistic assumptions about the cost of testing. Option B is incorrect, because the financial value of product quality can be estimated, for example, by using cost-benefit analysis, return on investment, or cost of quality models. Option C is incorrect, because going by cost as an exit criterion does not necessarily constrain the testing project or help achieve the desired quality level. Cost is a relative and variable factor that depends on the scope, complexity, and context of the software product and the testing project. Option D is incorrect, because the cost of testing can be measured effectively, for example, by using metrics, such as test effort, test resources, test tools, test environment, etc.

• Question 303:

  Which metric is MOST useful for measuring test execution progress?

  A. Number of requirements documented
  B. Percentage of test cases executed
  C. Number of developers per module
  D. Size of the codebase
  B. Percentage of test cases executed

  ---

  Explanation

  Execution progress is tracked by completed vs. planned test cases.

• Question 304:

  Which of the following statements about checklist-based testing is TRUE?

  A. Checklist-based testing is a technique for managing the review meeting that can be applied in those reviews where the use of checklists is mandatory, as is often the case in formal reviews.
  B. Checklist-based testing is a review technique that can be used in a formal review process where reviewers, during individual review, try to detect issues within the work product based on a checklist
  C. In checklist-based testing, using checklists at a high level of detail is more likely to produce test cases that are easier to reproduce than those using checklists at a low level of detail
  D. Checklists used in checklist-based testing should be reviewed periodically for updates as, over time, test cases designed using the same checklist may become less effective at finding defects.
  D. Checklists used in checklist-based testing should be reviewed periodically for updates as, over time, test cases designed using the same checklist may become less effective at finding defects.

  ---

  Explanation

  Checklist-based testing is a technique where testers use pre-determined checklists to ensure that important aspects of a work product are evaluated. Over time, these checklists should be reviewed and updated periodically to maintain their effectiveness in detecting defects. As systems evolve, outdated checklists may miss new types of defects, thus diminishing their usefulness. Therefore, statement D is true according to the ISTQB CTFL syllabus.

• Question 305:

  Which of the following best describes the relationship between a test progress report and a test summary report?

  A. The test report prepared during a test activity may be referred to as a test progress report, while a test report prepared at the end of a test activity may be referred to as a test summary report.
  B. The test report prepared during a test activity may be referred to as a test summary report, while a test report prepared at the end of a test activity may be referred to as a test progress report.
  C. There is no difference between a test progress report and a test summary report.
  D. Both the test progress report and the test summary report should always be generated via an automated tool.
  A. The test report prepared during a test activity may be referred to as a test progress report, while a test report prepared at the end of a test activity may be referred to as a test summary report.

  ---

  Explanation

  A test progress report is prepared during a test activity and provides updates on the current status of testing activities, including progress made, issues encountered, and test metrics. A test summary report, on the other hand, is prepared at the end of a test activity and provides a comprehensive overview of the testing carried out, including the final status, test results, defect summaries, and overall conclusions.

  ISTQB CTFL Syllabus V4.0, Section 5.3.2

• Question 306:

  Which of the following statements is the BEST example of non-functional testing?

  A. Tests which capture the time it takes to save a file
  B. Tests which calculate overtime pay for those employees entitled to such
  C. Tests related to "what" the system should do
  D. Tests based on the internal structure of a component or system
  A. Tests which capture the time it takes to save a file

  ---

  Explanation

  Non-functional testing refers to testing aspects that do not relate to specific behaviors or functions of the software but to attributes such as performance, usability, reliability, etc. Tests that capture the time it takes to save a file directly relate to the performance of the system, thus falling under non-functional testing.

  References:ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 1.2.5 "Functional and Non- functional Testing".

• Question 307:

  The acceptance criteria associated with a user story:

  A. are often written in a rule-oriented format using the template referred to as "Given/When/Then"
  B. are often documented following in rule-oriented format using the following template: "As a [role], I want [feature], so that I can [benefit]"
  C. can be written in different formats and represent an aspect of a user story referred to as confirmation' of the so called "3 C's"
  D. must be written in one of the two following formats: scenario-oriented or rule-oriented
  C. can be written in different formats and represent an aspect of a user story referred to as confirmation' of the so called "3 C's"

  ---

  Explanation

  The acceptance criteria associated with a user story are the conditions that must be met for the user story to be considered done and to deliver the expected value to the user. They are often written in different formats, such as rule-oriented, scenario-oriented, or table-oriented, depending on the nature and complexity of the user story. They represent an aspect of a user story referred to as confirmation, which is one of the so called "3 C' s" of user stories. The other two aspects are card and conversation. Card refers to the concise and informal description of the user story, usually following the template: "As a [role], I want [feature], so that I can [benefit]". Conversation refers to the ongoing dialogue between the stakeholders and the team members to clarify and refine the user story and its acceptance criteria. Therefore, option C is the correct answer.ISTQB Certified Tester Foundation Level Syllabus v4.01, Section 3.2.2, page 35-36; ISTQB Glossary v4.02, page 37.

• Question 308:

  Which of the following CORRECTLY matches the roles and responsibilities in a formal review?

  A. Facilitator - Fixes defects in the work product under review
  B. Scribe - Collates potential defects found during the individual review activity
  C. Review Leader - Creates the work product under review
  D. Author - Identify potential defects in the work product under review
  B. Scribe - Collates potential defects found during the individual review activity

  ---

  Explanation

  In formal reviews, the scribe's role is to collate potential defects and other findings during the review process. This position is crucial as it ensures all observations and defects are recorded accurately, facilitating efficient analysis and resolution of issues identified during the review.

  References:ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 3.2.4 "Roles and Responsibilities in a Formal Review".

• Question 309:

  Consider the following code

  int premium=2500;

  if (age<30)

  {

  premium = premium +1500: }

  Which options suits for a correct combination of Boundary value and expected result. Assume first number as boundary followed by expected result.

  A. 29, 1500 30. 2500
  B. 29. 4000 30. 2500
  C. 29, 2500 30. 1500
  D. 30, 1500 31,2500
  B. 29. 4000 30. 2500

  ---

  Explanation

  In the given code snippet, the premium is increased by 1500 if the age is less than 30. Therefore, at the boundary value of age 29, the premium should be 2500 + 1500 = 4000, and at age 30, the premium should remain at its initial value of 2500, as the condition is no longer met. Option B correctly reflects this with 29, 4000 and 30, 2500 as the boundary value and the expected results, respectively.

• Question 310:

  Which of the following statements about white-box testing is FALSE?

  A. Static testing can benefit from using code-related white-box test techniques during code reviews.
  B. White-box testing allows suggesting test cases for increasing coverage levels which are based on objective measures
  C. Achieving full code coverage for a component or a system ensures that it has been fully tested
  D. Black-box testing can benefit from using code-related white-box test techniques to increase confidence in the code.
  C. Achieving full code coverage for a component or a system ensures that it has been fully tested

  ---

  Explanation

  Achieving full code coverage does not guarantee that the component or system is fully tested or free of defects. Code coverage metrics indicate the extent to which the source code has been tested, but they do not account for the quality of the tests or whether all possible scenarios have been considered. Other types of testing, including functional, performance, and security testing, are necessary to ensure comprehensive testing. The ISTQB CTFL Syllabus v4.0 highlights that while high code coverage is beneficial, it does not equate to complete testing.