ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 171:

  Which activity is NOT documented in a test plan?

  A. Defining the quality assurance approach
  B. Defining the test approach
  C. Selecting the metrics for test monitoring
  D. Setting the budget for the test activities
  D. Setting the budget for the test activities

  ---

  Explanation

• Question 172:

  A requirement specifies that a certain identifier (ID) must be between 5 and 10 characters long, must contain only alphanumeric characters, and its first character must be a letter As a tester, you want to apply one- dimensional equivalence partitioning to test this ID. This means that you have to apply equivalence partitioning individually: to the length of the ID, the type of characters contained within the ID, and the type of the first character of the ID. What is the number of partitions to cover?

  A. 7.
  B. 6.
  C. 5.
  D. 3.
  A. 7.

  ---

  Explanation

  To apply one-dimensional equivalence partitioning to the ID requirement, we need to consider each condition individually:

  Length of the ID: Valid partitions (5-10 characters), Invalid partitions (less than 5, more than 10) = 3 partitions.

  Type of characters: Valid partitions (alphanumeric), Invalid partitions (non-alphanumeric) = 2 partitions.

  First character: Valid partitions (letter), Invalid partitions (non-letter) = 2 partitions. Adding these partitions, we get a total of 3 (length) + 2 (character type) + 2 (first character) = 7 partitions. Thus, the correct answer is A.

• Question 173:

  Which of the following is an example of scenario-oriented acceptance criteria?

  A. The user should be able to provide three inputs to test the product - the Al model to be tested, the data used and an optional text file
  B. Verify that a registered user can create add a new project with name having more than 100 characters
  C. A user is already logged in then on navigating to the Al model testing page the user should be directly shown the report of last test run.
  D. An unregistered user shouldn't be shown any report
  C. A user is already logged in then on navigating to the Al model testing page the user should be directly shown the report of last test run.

  ---

  Explanation

• Question 174:

  Which of the following is NOT a common objective of testing?

  A. Finding defects in the software
  B. Preventing defects
  C. Debugging the software to find the reason for defects
  D. Providing information on the status of the system
  C. Debugging the software to find the reason for defects

  ---

  Explanation

  Debugging the software to find the reason for defects is not a common objective of testing, but rather a task of development or maintenance. Debugging is a process of locating and fixing errors in the software code, while testing is a process of finding and reporting defects in the software behavior or quality. Testing does not aim to fix defects, but rather to provide information on their existence and impact. The other options are common objectives of testing. Finding defects in the software is one of the main objectives of testing, as it helps to improve the quality and reliability of the software. Preventing defects is another objective of testing, as it helps to avoid rework and reduce costs and risks. Providing information on the status of the system is another objective of testing, as it helps to support decision making and risk management. Verified

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

• Question 175:

  Which statement is true regarding confirmation testing and regression testing?

  A. Confirmation testing confirms the quality of the test being run while regression testing ensures that the software still works after a change has been made.
  B. Confirmation testing is an optional activity whilst regression testing is not negotiable.
  C. Confirmation testing aims to verify that a defect has been resolved and regression testing ensuring that existing functionality still works after a change.
  D. Testers' involvement is essential whilst running retesting and regression testing.
  E. TESTER Involvement is essential whilst running retesting and regression testing.
  C. Confirmation testing aims to verify that a defect has been resolved and regression testing ensuring that existing functionality still works after a change.

  ---

  Explanation

  Confirmation testing, also known as retesting, is conducted to verify that specific defects have been fixed. Regression testing, on the other hand, is performed to ensure that recent changes have not adversely affected existing features of the software. Both types of testing are crucial for maintaining the integrity and quality of the software after modifications.

• Question 176:

  "Statement Testing" is part of;

  A. Specification Based testing
  B. Decision Testing
  C. Experience based testing
  D. Structured based testing
  D. Structured based testing

  ---

  Explanation

  Statement Testing is a type of white-box testing technique where the test cases are designed based on the implementation of the software, specifically aiming to execute every statement in the code at least once. This falls under the category of structure-based testing (also known as white-box testing), where the internal structure of the system is used to design test cases. Therefore, option D is correct.

• Question 177:

  Which of the following statements regarding the testing quadrants model is correct?

  A. The testing quadrants model provides a way of differentiating between types of tests and assists in explaining them to stakeholders.
  B. The testing quadrants model assigns test types to the corresponding V-Model test levels.
  C. With the testing quadrants model, tests can be either business-oriented or product-oriented.
  D. The testing quadrants model assigns tests from one of the four quadrants to each iteration in the Agile development.
  A. The testing quadrants model provides a way of differentiating between types of tests and assists in explaining them to stakeholders.

  ---

  Explanation

• Question 178:

  Which of the following is an example of black-box dynamic testing?

  A. Functional Testing
  B. Code inspection
  C. Checking memory leaks for a program by executing it
  D. Coverage analysis
  A. Functional Testing

  ---

  Explanation

  Functional testing is an example of black-box dynamic testing. Black-box testing (also known as specification-based testing) is a type of testing that does not consider the internal structure or implementation of the system under test, but rather its external behavior or functionality. Dynamic testing is a type of testing that involves executing the system under test with various inputs and observing its outputs. Functional testing is a type of black-box dynamic testing that verifies that the system under test performs its intended functions according to its requirements or specifications. Functional testing can be performed at various levels and scopes depending on the objectives and criteria of testing. The other options are not examples of black-box dynamic testing. Code inspection is an example of white-box static testing. White-box testing (also known as structure-based testing) is a type of testing that considers the internal structure or implementation of the system under test. Static testing is a type of testing that does not involve executing the system under test, but rather analyzing it for defects, errors, or violations of standards. Code inspection is a type of white-box static testing that involves examining the source code of the system under test for quality, readability, maintainability, etc. Checking memory leaks for a program by executing it is an example of white-box dynamic testing. Memory leaks are defects that occur when a program fails to release memory that it has allocated but no longer needs. Checking memory leaks for a program by executing it requires knowledge and access to the internal structure or implementation of the program, such as memory allocation and deallocation mechanisms, pointers, references, etc. Coverage analysis is an example of white-box static testing. Coverage analysis is a technique that measures how much of the code or structure of the system under test has been exercised by a test suite. Coverage analysis requires knowledge and access to the internal structure or implementation of the system under test, such as statements, branches, paths, conditions, etc. Verified

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

• Question 179:

  Which of the following statements about exploratory testing is true?

  A. Exploratory testing is an experience-based test technique in which testers explore the requirements specification to detect non testable requirements
  B. When exploratory testing is conducted following a session-based approach, the issues detected by the testers can be documented in session sheets
  C. Exploratory testing is an experience-based test technique used by testers during informal code reviews to find defects by exploring the source code
  D. In exploratory testing, testers usually produce scripted tests and establish bidirectional traceability between these tests and the items of the test basis
  B. When exploratory testing is conducted following a session-based approach, the issues detected by the testers can be documented in session sheets

  ---

  Explanation

  Exploratory testing is an experience-based test technique in which testers dynamically design and execute tests based on their knowledge, intuition, and learning of the software system, without following predefined test scripts or test cases.

  Exploratory testing can be conducted following a session-based approach, which is a structured way of managing and measuring exploratory testing. In a session-based approach, the testers perform uninterrupted test sessions, usually

  lasting between 60 and 120 minutes, with a specific charter or goal, and document the issues detected, the test coverage achieved, and the time spent in session sheets. Session sheets are records of the test activities, results, and

  observations during a test session, which can be used for reporting, debriefing, and learning purposes. The other statements are false, because:

  Exploratory testing is not a test technique in which testers explore the requirements specification to detect non testable requirements, but rather a test technique in which testers explore the software system to detect functional and nonfunctional defects, as well as to learn new information, risks, or opportunities. Non testable requirements are requirements that are ambiguous, incomplete, inconsistent, or not verifiable, which can affect the quality and effectiveness of the

  testing process. Non testable requirements can be detected by applying static testing techniques, such as reviews or inspections, to the requirements specification, before the software system is developed or tested. Exploratory testing is not

  a test technique used by testers during informal code reviews to find defects by exploring the source code, but rather a test technique used by testers during dynamic testing to find defects by exploring the behavior and performance of the

  software system, without examining the source code. Informal code reviews are static testing techniques, in which the source code is analyzed by one or more reviewers, without following a formal process or using a checklist, to identify

  defects, violations, or improvements. Informal code reviews are usually performed by developers or peers, not by testers. In exploratory testing, testers usually do not produce scripted tests and establish bidirectional traceability between

  these tests and the items of the test basis, but rather produce unscripted tests and adapt them based on the feedback and the findings of the testing process. Scripted tests are tests that are designed and documented in advance, with

  predefined inputs, outputs, and expected results, and are executed according to a test plan or a test procedure. Bidirectional traceability is the ability to trace both forward and backward 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. Scripted tests and bidirectional traceability are usually associated with more formal and structured testing

  approaches, such as specification-based or structure-based test techniques, not with exploratory testing.

  References:

  ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

  ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.3, Experience-based Test Design Techniques1

  ISTQB Glossary of Testing Terms v4.0, Exploratory Testing, Session-based Testing, Session Sheet, Non Testable Requirement, Static Testing, Informal Review, Dynamic Testing, Scripted Testing, Bidirectional Traceability2

• Question 180:

  Which of the following are the phases of the ISTQB fundamental test process?

  A. Test planning and control, Test analysis and design, Test implementation and execution, Evaluating ex t criteria and reporting. Test closure activities
  B. Test planning, Test analysis and design. Test implementation and control. Checking test coverage and reporting, Test closure activities
  C. Test planning and control, Test specification and design. Test implementation and execution, Evaluating test coverage and reporting, Retesting and regression testing, Test closure activities
  D. Test planning. Test specification and design. Test implementation and execution. Evaluating exit criteria and reporting. Retesting and test closure activities
  A. Test planning and control, Test analysis and design, Test implementation and execution, Evaluating ex t criteria and reporting. Test closure activities

  ---

  Explanation

  The ISTQB fundamental test process consists of five main phases, as described in the ISTQB Foundation Level Syllabus, Version 4.0, 2018, Section 2.2, page 15:

  Test planning and control: This phase involves defining the test objectives, scope, strategy, resources, schedule, risks, and metrics, as well as monitoring and controlling the test activities and results throughout the test process. Test analysis

  and design: This phase involves analyzing the test basis (such as requirements, specifications, or user stories) to identify test conditions (such as features, functions, or scenarios) that need to be tested, and designing test cases and test

  procedures (such as inputs, expected outcomes, and execution steps) to cover the test conditions. This phase also involves evaluating the testability of the test basis and the test items (such as software or system components), and selecting

  and implementing test techniques (such as equivalence partitioning, boundary value analysis, or state transition testing) to achieve the test objectives and optimize the test coverage and efficiency. Test implementation and execution: This

  phase involves preparing the test environment (such as hardware, software, data, or tools) and testware (such as test cases, test procedures, test data, or test scripts) for test execution, and executing the test procedures or scripts according

  to the test plan and schedule. This phase also involves logging the outcome of test execution, comparing the actual results with the expected results, and reporting any discrepancies as incidents (such as defects, errors, or failures).

  Evaluating exit criteria and reporting: This phase involves checking if the planned test activities have been completed and the exit criteria (such as quality, coverage, or risk levels) have been met, and reporting the test results and outcomes to

  the stakeholders. This phase also involves making recommendations for the release or acceptance decision based on the test results and outcomes, and identifying any residual risks (such as known defects or untested areas) that need to be

  addressed or mitigated.

  Test closure activities: This phase involves finalizing and archiving the testware and test environment for future reuse, and evaluating the test process and the test project against the test objectives and the test plan. This phase also involves

  identifying any lessons learned and best practices, and communicating the findings and suggestions for improvement to the relevant parties.

  References:

  ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.2, page 15;

  ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 37-38; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, question88, page 32.