ISTQB-CTFL Exam Questions Instant Access - No Installation Required

Question 1

In a two-hour uninterrupted test session, performed as part of an iteration on an Agile project, a heuristic checklist was used to help the tester focus on some specific usability issues of a web application.

The unscripted tests produced by the tester's experience during such session belong to which one of the following testing quadrants?

AQ1

BQ2

CQ3

DQ4

Answer : C

The unscripted tests produced by the tester's experience during the two-hour test session belong to the testing quadrant Q3. The testing quadrants are a classification of testing types based on two dimensions: the test objectives (whether the testing is focused on supporting the team or critiquing the product) and the test basis (whether the testing is based on the technology or the business). The testing quadrants are labeled as Q1, Q2, Q3, and Q4, and each quadrant represents a different testing perspective, such as unit testing, acceptance testing, usability testing, or performance testing. The testing quadrant Q3 corresponds to the testing types that have the objective of critiquing the product from the business perspective, such as exploratory testing, usability testing, user acceptance testing, alpha testing, beta testing, etc. The unscripted tests performed by the tester in the given scenario are examples of exploratory testing and usability testing, as they are based on the tester's experience, intuition, and learning of the web application, and they focus on some specific usability issues, such as the user interface, the user satisfaction, the user feedback, etc. The other options are incorrect, because:

The testing quadrant Q1 corresponds to the testing types that have the objective of supporting the team from the technology perspective, such as unit testing, component testing, integration testing, system testing, etc. These testing types are usually performed by developers or testers who have access to the source code, the design, the architecture, or the configuration of the software system, and they aim to verify the functionality, the quality, and the reliability of the software system at different levels of integration.

The testing quadrant Q2 corresponds to the testing types that have the objective of supporting the team from the business perspective, such as functional testing, acceptance testing, story testing, scenario testing, etc. These testing types are usually performed by testers or customers who have access to the requirements, the specifications, the user stories, or the business processes of the software system, and they aim to validate that the software system meets the expectations and the needs of the users and the stakeholders.

The testing quadrant Q4 corresponds to the testing types that have the objective of critiquing the product from the technology perspective, such as performance testing, security testing, reliability testing, compatibility testing, etc. These testing types are usually performed by testers or specialists who have access to the tools, the metrics, the standards, or the benchmarks of the software system, and they aim to evaluate the non-functional aspects of the software system, such as the efficiency, the security, the reliability, or the compatibility of the software system under different conditions or environments.Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 1.3.1, Testing in Software Development Lifecycles

ISTQB Glossary of Testing Terms v4.0, Testing Quadrant, Exploratory Testing, Usability Testing, Unit Testing, Component Testing, Integration Testing, System Testing, Functional Testing, Acceptance Testing, Story Testing, Scenario Testing, Performance Testing, Security Testing, Reliability Testing, Compatibility Testing

Question 2

Which of the following is a test-first approach, where tests that express a shared understanding from stakeholders of how the application is expected to work, are first written in business-readable language (following the Given/When/Then format), and then made executable to drive development?

ATest-Driven Development (TDD)

BAcceptance Test-Driven Development (ATDD)

CBehavior-Driven Development (BDD)

DDomain-Driven Design (DDD)

Answer : C

This answer is correct because Behavior-Driven Development (BDD) is a test-first approach, where tests that express a shared understanding from stakeholders of how the application is expected to work, are first written in business-readable language (following the Given/When/Then format), and then made executable to drive development. BDD is a collaborative approach that involves testers, developers, business analysts, product owners, and other stakeholders in defining the expected behavior of the application using scenarios that describe the preconditions, actions, and outcomes of the application. BDD scenarios are written using a domain-specific language (DSL) that can be translated into executable test cases using tools such as Cucumber or SpecFlow. BDD aims to improve communication, collaboration, and feedback among the team members, and to deliver software that meets the customer's needs and expectations.Reference: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 3.1.1.4

,Requirements Engineering Fundamentals.

Question 3

Which ONE of the following options MOST ACCURATELY describes the activities of ''testing'' and ''debugging''?

ATesting triggers a failure that is caused by a defect in the software, whereas debugging is concerned with finding the causes of this failure (defects), analyzing these causes, and eliminating them.

BTesting triggers a failure that is caused by a defect in the software, whereas debugging is concerned with finding the causes of this failure (defects), analyzing these causes, and reproducing them.

CTesting identifies a defect that is caused by an error in the software, whereas debugging is concerned with finding the causes of this defect, analyzing these causes, and eliminating them.

DTesting triggers a defect that is caused by an error in the software, whereas debugging is concerned with finding the causes of this defect, analyzing these causes, and eliminating them.

Answer : A

Comprehensive and Detailed In-Depth Explanation:

Testing and debugging are separate but related activities. Testing executes the software to identify failures that result from defects (A). Debugging is the developer's responsibility and involves finding the cause of a failure (defect), analyzing it, and fixing the defect. The ISTQB syllabus explicitly differentiates these activities. Testing does not modify the software, whereas debugging does.

Question 4

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

AIt 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.

BIt 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

CIt helps the whole team be more effective in test case design by requiring all team members to master all types of test techniques.

DIt helps team members develop better relationships with each other and make their collaboration more effective for the benefit of the project.

Answer : D

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 5

The following state diagram is given as basis for state transition testing and contains only valid transitions:

Explanation of the state diagram: States are depicted as nodes. The initial state is I, the final state is F. A state transition is depicted as a directed arrow with the initiating event as a label, e. g. from I to S1 with event a, and is also written as a triple (I,a,S1). Note: A test case is a sequence of events that initiates the corresponding sequence of state transitions.

The state diagram contains the following 7 state transitions:

(I, a, S1)

(S1, a, S2), (S1, b, S3), (S1, c, F)

(S2, a, S3)

(S3, a, S2), (S3, b, F)

What is the minimum number of test cases to achieve 100% coverage of all valid state transitions in the diagram?

Answer : C

Question 6

What is typically NOT included in a test progress report?

AInformation about test obstacles during a test period

BStatistics on the success of each tester in finding bugs

CChanged risks within the test period

DTest status in relation to defined test metrics (including exit criteria)

Answer : B

Question 7

A class grade application for instructors assigns letter grades based on students' numerical grades.

The letter grades for different numerical grades should be:

Above 89, up to 100 - A

Above 79, up to 89 * B

Above 69, up to 79 * C

Above 59, up to 69 - D

Below 60 - F

Which of the following sets of test inputs would achieve the relatively highest equivalence partition coverage?

A0, 58.59,70, 80

B74, 79.84,85, 89

C79, 89.90,99, 100

D69, 79. 80, 89, 90

Answer : D

The set of test inputs that achieve the relatively highest equivalence partition coverage for grading students is option D: 69, 79, 80, 89, 90. This set effectively tests the boundaries between each grade category, ensuring that the grading system accurately transitions from one grade to another at the correct thresholds (ISTQB Main Web). Reference:

ISTQB Certified Tester Foundation Level Syllabus v4.0: ISTQB CTFL Syllabus v4.0 PDF

ISTQB Certified Tester Foundation Level v4.0 ISTQB-CTFL Exam Questions