CTFL_Syll2018 Exam Dumps - ISTQB Certified Tester Foundation Level (Syllabus 2018)

Use case testing does not find defects caused by interaction of different components is the statement that is false about use case testing. Use case testing is a technique to create test cases based on use cases, which are descriptions of how a system interacts with one or more actors (users or other systems) to achieve a specific goal or function. Use case testing can find defects caused by interaction of different components, as use cases often involve multiple components working together to provide a service or functionality to an actor2 explains use case testing as follows:

Use case testing is a technique that helps us identify test cases that exercise the whole system on a transaction by transaction basis from start to finish. It is a functional black box testing technique.

Use cases are prepared by analysts and domain experts who document the functional requirements of a system from an end-user perspective. Each use case typically has a mainstream scenario and may have alternate or exceptional scenarios that describe different paths or outcomes.

Use case testing can help to verify that all the interactions between actors and the system under test work as expected and meet the user requirements. It can also help to detect integration defects between different components or subsystems.

A, B, and D are correct statements about use case testing. Use case generally has a mainstream scenario and may have many alternate or exceptional scenarios (A), as use cases describe different paths or outcomes depending on various conditions or events. A use case can be defined at different levels of abstraction, such as user goal level, summary level, subfunction level, etc., but not at the abstract level detached from the implementation or at the system level describing a set of executed functions (B), as use cases always describe interactions between actors and systems rather than abstract concepts or functions. Each use case has preconditions which need to be met for the use case to work successfully (D), as preconditions specify what must be true before a use case can begin.

Agile development can be classified as an iterative incremental life cycle model, where each iteration delivers a working product increment that can be evaluated by stakeholders and users. describes this as follows:

Iterative Incremental Development Model is a process where creating requirements, designing, building and testing a system in small parts. This model divided into small parts which will help to make modules very easily.In this model, module passes through some phases like requirements, coding, designing, testing.

Agile Model mostly recommended to use for current software development industries because it is very realistic approach to develop any kind of software.It follows iterative approach which means whole project divided into small iterations or modules.

Agile development is not related to any life cycle model (A), RAD (B), or V model ©.

Test design is the process of transforming general testing objectives into tangible test conditions and test cases that can be executed and verified against expected results. Test design involves identifying test techniques, coverage criteria, input data, expected outcomes and other test parameters.

Configuration management is related to ensuring the integrity of the testware, as it is a process that controls and documents changes to test items, test cases, test data, test scripts, test results, and test documentation throughout the testing lifecycle. The other options are not related to ensuring the integrity of the testware, but to other aspects of testing such as test execution, test environment setup, and test planning.

References: Section 4.1, Section 4.2

A peer review is a review done by colleagues at the same organizational level, such as developers, testers, or managers. An informal review without moderator is called a walkthrough. A review done by developers and testers together is called an inspection. A review done by developers only is not a specific type of review.

References: Certified Tester Foundation Level (CTFL) Syllabus - ASTQB, Section 3.1.1, Page 18

Product risk analysis is an approach to testing that aims to reduce the level of product risks and inform stakeholders of their status, starting in the initial stages of a project1. It involves the identification of product risks and the use of risk levels to guide the test process1. Product risks are uncertain situations that can affect the quality or value of the software product2. One of the factors that can influence the testing approach is the test design technique to be applied3. Test design techniques are methods to derive and select test cases based on the test objectives, test conditions, and test basis2. Decision table testing is a test design technique that is suitable for testing complex business rules that have logical conditions and outcomes2. Therefore, if the product risk analysis identifies that the complex business rules could result in costly failures, then decision table testing will be used for test case design to cover all the possible combinations of conditions and outcomes2.

The other options are not examples of how product risk analysis can influence the testing approach, because they are either not related to product risks or not based on risk levels. They are:

• Performance failures were much lower than expected, so more test analysis will be conducted in this area (B). This is not related to product risk analysis, but to test monitoring and control, which is the process of comparing actual progress against the plan and reporting the status2. Test analysis is the activity of analyzing the test basis and defining test objectives2. If the performance failures were much lower than expected, then more test execution or evaluation might be needed, not more test analysis.
• There is a lack of automation skills in the test team, so training for the automation tool will be rolled out ©. This is not related to product risk analysis, but to test management, which is the process of planning, monitoring, and controlling the test activities and resources2. Test automation is the use of software to perform or support test activities2. The lack of automation skills in the test team is a project risk, not a product risk, and it should be addressed by providing adequate training, tools, and resources for the test team2.
• There are no product risks recorded around security, so security testing will be given priority as a contingency measure (D). This is not based on risk levels, but on the absence of risk identification, which is a poor practice in product risk analysis. Security testing is a type of testing that determines whether the software protects data and maintains functionality as intended2. Product risk analysis should identify the potential security risks and assign them appropriate risk levels based on their probability and impact1. Security testing should be prioritized based on the risk levels, not on the lack of risk identification, which could lead to overlooking or underestimating the security risks1.

References:

• ISTQB Foundation Level 2018 syllabus
• Risk in Software Testing
• Risk-Based Testing
• Test Approach

A key difference between black box and white box test design techniques is that white box techniques can measure the extent of code coverage, while black box techniques cannot. Code coverage is a measure of how much of the code of a system or component has been executed by a test or a set of tests. White box techniques use software code to derive test cases that cover specific aspects of the code, such as statements, branches, paths, or data flows. White box techniques can use tools or methods to measure the code coverage achieved by the test cases and identify any gaps or redundancies. Black box techniques use functional design specifications to derive test cases that cover specific aspects of the functionality, behavior, or quality of the system or component, such as inputs, outputs, equivalence classes, boundary values, states, transitions, etc. Black box techniques do not use or access the code of the system or component, and therefore cannot measure the code coverage.

References: Certified Tester Foundation Level Syllabus, Section 4.3 and 4.4

According to the syllabus, configuration management is a process that establishes and maintains the consistency of a product’s attributes throughout its life cycle. It involves identifying, controlling, tracking, and auditing changes to the product’s components and documentation. Configuration management supports the test process by enabling the tester to reproduce the tested item through unique identification and version control. This ensures that the tester knows exactly what has been tested and can trace any defects or incidents to the correct version of the software under test. The answer A is correct because it best describes how configuration management supports the test process. The other answers are incorrect because they describe other aspects of testing that are not directly related to configuration management.

References: Certified Tester Foundation Level Syllabus, Section 2.2.1, page 22-23.