ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 161:

  Which option BEST describes the purpose of traceability between test basis and test cases?

  A. To measure developer productivity
  B. To confirm that all requirements are tested
  C. To estimate system performance
  D. To reduce review time
  B. To confirm that all requirements are tested

  ---

  Explanation

  Traceability ensures full requirements coverage through test cases.

• Question 162:

  Which test level aims to gain the users' confidence in the system, especially in the fulfillment of the system's operational and performance capabilities?

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

  ---

  Explanation

• Question 163:

  Which of the following statements about the value of maintaining traceability between the test basis and test work products is not true?

  A. Traceability can be useful for assessing the impact of a change to a test basis item on the corresponding tests
  B. Traceability can be useful for determining how many test basis items are covered by the corresponding tests
  C. Traceability can be useful for determining the most suitable test techniques to be used in a testing project
  D. Traceability can be useful to support the needs required by the auditing of testing
  C. Traceability can be useful for determining the most suitable test techniques to be used in a testing project

  ---

  Explanation

  Traceability is the ability to trace the relationships between the items of the test basis, such as the requirements, the design, the risks, etc., and the test artifacts, such as the test cases, the test results, the defects, etc. Traceability can provide various benefits for the testing process, such as improving the test coverage, the test quality, the test efficiency, and the test communication. However, not all the statements given are true about the value of maintaining traceability between the test basis and test work products. The statement that is not true is option C, which says that test objectives should be the same for all test levels, although the number of tests designed at various levels can vary significantly. This statement is false, because test objectives are the goals or the purposes of testing, which can vary depending on the test level, the test type, the test technique, the test environment, the test stakeholder, etc. Test objectives can be defined in terms of the test basis, the test coverage, the test quality, the test risk, the test cost, the test time, etc. Test objectives should be specific, measurable, achievable, relevant, and time-bound, and they should be aligned with the project objectives and the quality characteristics. Test objectives should not be the same for all test levels, as different test levels have different focuses, scopes, and perspectives of testing, such as component testing, integration testing, system testing, and acceptance testing. The other statements are true about the value of maintaining traceability between the test basis and test work products, such as: Traceability can be useful for assessing the impact of a change to a test basis item on the corresponding tests: This statement is true, because traceability can help to identify which tests are affected by a change in the test basis, such as a new requirement, a modified design, a revised risk, etc., and to determine the necessary actions to update, re-execute, or re-evaluate the tests. Traceability can also help to estimate the effort, the cost, and the time needed to implement the change and to verify its impact on the software system. Traceability can be useful for determining how many test basis items are covered by the corresponding tests: This statement is true, because traceability can help to measure the test coverage, which is the degree to which the test basis is exercised by the test cases. Traceability can help to identify which test basis items are covered, partially covered, or not covered by the tests, and to evaluate the adequacy, the completeness, and the effectiveness of the testing process. Traceability can also help to identify the gaps, the overlaps, or the redundancies in the test coverage, and to prioritize, optimize, or improve the test cases. Traceability can be useful to support the needs required by the auditing of testing: This statement is true, because traceability can help to provide evidence, documentation, and justification for the testing activities, results, and outcomes. Traceability can help to demonstrate that the testing process follows the standards, the regulations, the policies, and the best practices that are applicable to the software system, the project, or the organization. Traceability can also help to verify that the testing process meets the expectations, the needs, and the satisfaction of the users and the stakeholders.

  References : ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents: ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 1.2.2, Testing Policies, Strategies, and Test Approaches1 ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.1, Test Planning1 ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.2, Test Monitoring and Control1 ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.3, Test Analysis and Design1 ISTQB Glossary of Testing Terms v4.0, Traceability, Test Basis, Test Artifact, Test Objective, Test Level, Test Coverage, Test Quality, Test Risk, Test Cost, Test Time2

• Question 164:

  Which of the following statements about impact of DevOps on testing is CORRECT?

  A. DevOps helps eliminate manual testing by having focus on continuous automated testing
  B. DevOps helps shift focus of testing people to perform operations testing
  C. DevOps helps bring focus on testing of non-functional characteristics
  D. DevOps helps shift focus of operations people to functional testing
  A. DevOps helps eliminate manual testing by having focus on continuous automated testing

  ---

  Explanation

• Question 165:

  Which one of the following statements IS NOT a valid objective of testing?

  A. To build confidence in the level of quality of the test object.
  B. To find all defects in a product, ensuring the product is defect free.
  C. To find failures and defects
  D. To evaluate work products such as requirements, user stories, design, and code.
  B. To find all defects in a product, ensuring the product is defect free.

  ---

  Explanation

  Finding all defects in a product and ensuring it is defect-free is not a valid objective of testing. Testing aims to find as many defects as possible, build confidence in the quality of the product, and evaluate work products. However, it is unrealistic to expect testing to find all defects, and declaring a product completely defect-free is impractical.

  ISTQB CTFL Syllabus V4.0, Section 1.1.1

• Question 166:

  Which of the following statements refers to a good testing practice that applies to all software development lifecycles?

  A. Each test level should have its own specific test objectives that should be consistent with the software development lifecycle phase or type of activities it addresses.
  B. Test analysis and design for any test levels should begin as soon as coding is complete, and all system components are available for testing
  C. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  D. All the tests should be automated and run as part of the continuous integration process with every software change
  A. Each test level should have its own specific test objectives that should be consistent with the software development lifecycle phase or type of activities it addresses.

  ---

  Explanation

  Good testing practice dictates that each test level (e.g., unit testing, integration testing, system testing) should have distinct test objectives aligned with the phase of the software development lifecycle it addresses. This ensures that testing is effective and relevant at each stage. According to the ISTQB CTFL Syllabus v4.0, establishing clear test objectives that are consistent with the development phase helps in achieving specific goals and improving the overall quality of the software product.

• Question 167:

  As a tester, as part of a V-model project, you are currently executing some tests aimed at verifying if a mobile app asks the user to grant the proper access permissions during the installation process and after the installation process. The requirements specification states that in both cases the app shall ask the user to grant access permissions only to the camera and photos stored on the device. However, you observe that the app also asks the user to grant access permission to all contacts on the device. Consider the following items:

  [I]. Test environment [ii]. Expected result [iii]. Actual result.

  [IV] Test level. [V]. Root cause.

  Based on only the given information, which of the items listed above, are you able to CORRECTLY specify in a defect report?

  A. [l] and [IV]
  B. [ii] and [III].
  C. [ii], [iii] and [v]
  D. [ii], [IV] and [V].
  B. [ii] and [III].

  ---

  Explanation

  When writing a defect report, the tester can specify the expected result and the actual result based on the observation. The expected result is what the requirements specify, and the actual result is what was observed during testing. These elements are crucial for clearly communicating the nature of the defect to developers and other stakeholders. The other items such as test environment, test level, and root cause may not be clear or necessary at this stage of defect reporting.

  References: ISTQB CTFL Syllabus, Section on defect management and reporting.

• Question 168:

  In addition to thorough testing of the requirements specification, a development team aims to involve users as early as possible in the development process, using practices such as prototyping, to ensure that the software systems being developed will meet the users' expectations. This approach is especially useful at mitigating the risks associated with one of the seven testing principles, which one?

  A. Tests wear out
  B. Absence-of-errors fallacy
  C. Working software over comprehensive documentation.
  D. Defects cluster together
  B. Absence-of-errors fallacy

  ---

  Explanation

  The absence-of-errors fallacy is the mistaken belief that just because a software system is free of defects, it will meet the user's needs and expectations. Involving users early through practices like prototyping helps ensure that the development team is building the right system that meets user expectations, not just a system that is defect-free. This approach aligns with the testing principle that emphasizes understanding the users' needs and ensuring the system fulfills them. This principle is explained in the ISTQB CTFL Syllabus v4.0.

• Question 169:

  The statement: "Test activities should start in the early stages of the lifecycle, adhering to the testing principle of early testing" is relevant to which of the recognized software development models?

  A. Sequential development model.
  B. Iterative development model.
  C. Incremental development model.
  D. All the above
  D. All the above

  ---

  Explanation

  The principle of early testing is applicable to all recognized software development models, including sequential, iterative, and incremental models. Starting test activities early in the lifecycle helps in identifying and addressing defects as soon as possible, which can save time and costs by preventing defects from propagating to later stages of development. This proactive approach enhances the overall quality and efficiency of the software development process.

  ISTQB CTFL Syllabus V4.0, Section 1.3

• Question 170:

  Which ONE of the following statements about acceptance testing is NOT correct?

  A. Testing of disaster recovery and backup/restore is usually NOT part of acceptance testing.
  B. The customers or system users are often responsible for the acceptance testing.
  C. The main goal of acceptance testing is to build confidence in the system, not find defects.
  D. Acceptance testing is the last level of testing performed prior to system release.
  A. Testing of disaster recovery and backup/restore is usually NOT part of acceptance testing.

  ---

  Explanation

  Acceptance testing is a level of testing performed to verify that a software product meets the agreed acceptance criteria and is acceptable for delivery. Acceptance testing is often performed by the customers or system users, who are the main stakeholders of the software product. The main goal of acceptance testing is to build confidence in the system, not find defects, as defects should have been detected and fixed in earlier levels of testing. Acceptance testing is the last level of testing performed prior to system release, unless there are any changes or fixes that require re-testing. Testing of disaster recovery and backup/restore is usually part of acceptance testing, as these are important aspects of system reliability and security that affect the customer satisfaction and trust. Therefore, statement A is not correct, while statements B, C and D are correct. Verified

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 2, page 20- 21.