ISTQB CTFL-2018 Practice Test - Questions Answers, Page 34

It describes how test cases are derived from a use case.A use case is a description of a set of sequences of actions, including variants, that a system performs to yield an observable result of value to an actor1. An actor can be a human user or another system.Test cases are designed to cover various user behaviors, including basic, exceptional or alternative and error behaviors associated with each use case1.Option A is incorrect, as test cases derived from a use case are not based on non-functional requirements such as usability, but on functional requirements that describe what the system does1.Option C is incorrect, as test cases derived from a use case are not created using white-box test techniques, but using black-box test techniques that focus on the inputs and outputs of the system1.Option D is incorrect, as test cases derived from a use case are not based on pair testing, which is a technique that involves two testers working together to find defects1.

Reference:1, Section 4.2.4

The correct answer is A, as it describes error guessing.Error guessing is an experience-based test technique that involves designing tests based on experience, defect data, or common knowledge about why software fails1.Error guessing can be used to complement other more formal test techniques by focusing on areas that are more likely to contain defects1.Option B is incorrect, as error guessing does not involve building test cases based on the various experiences of developers, architects, users, and other stakeholders on project teams, but based on the tester's own experience and knowledge1.Option C is incorrect, as error guessing is not a suitable test technique that can be used effectively in place of more formal techniques, but a supplementary technique that can be used in addition to more formal techniques1.Option D is incorrect, as error guessing is not a valid and useful white-box test technique due to its high degree of statement coverage, but an experience-based test technique that does not rely on the structure of the software1.

Reference:1, Section 4.2.6

The correct answer is D, as it describes exploratory testing.Exploratory testing is an experience-based test technique that involves simultaneous learning, test design, and test execution1. Exploratory testing may be used within defined time periods, during which the tester may follow a test charter as a guide.A test charter is a document that specifies the scope, objective, and approach of an exploratory testing session1.Option A is incorrect, as exploratory testing is not a suitable test technique that may replace both black-box and white-box test techniques, but a complementary technique that can be used along with other techniques1.Option B is incorrect, as exploratory testing does not require both solid specifications and much project time available for test execution, but can be used in situations where specifications are incomplete or changing and where time is limited1.Option C is incorrect, as exploratory testing is not a valid and useful black-box test technique since it focuses on test cases related to the architecture and design of a system, but an experience-based test technique that focuses on learning about the system and its behavior1.

Reference:1, Section 4.2.6

The correct answer is B, as it describes checklist-based testing.Checklist-based testing is an experience-based test technique that involves a list of tests based on what is important to the user as well as an understanding of why and how software fails1.Checklist-based testing can be used to ensure that important aspects of the software are tested and to guide the tester in creating additional tests1.Option A is incorrect, as checklist-based testing provides some consistency and guidelines concerning test case development by using predefined lists of items or criteria to check against1.Option C is incorrect, as checklist-based testing is not restricted to non-functional testing, but can be used for both functional and non-functional testing1.Option D is incorrect, as checklist-based testing does not include formal tests from detailed lists of test conditions, but informal tests from high-level lists of items or criteria1.

Reference:1, Section 4.2.6

The correct answer is D, as it describes tools that support reviews.Tools that support reviews are tools that assist with performing static testing activities such as checking documents for defects or compliance with standards3. Examples of tools that support reviews are:

Tools for document review and annotation

Tools for document comparison and version control

Tools for checklist management and defect tracking

Option A is incorrect, as it describes tools that support usability testing.Tools that support usability testing are tools that assist with performing dynamic testing activities related to how easy and user-friendly the software product is3. Examples of tools that support usability testing are:

Tools for recording user actions and feedback

Tools for analyzing user behavior and satisfaction

Tools for simulating different user interfaces and devices

Option B is incorrect, as it describes tools that assess data quality.Tools that assess data quality are tools that assist with evaluating and improving the accuracy and completeness of data used for testing3. Examples of tools that assess data quality are:

Tools for data validation and verification

Tools for data cleansing and transformation

Tools for data profiling and analysis

Option C is incorrect, as it describes tools that support specialized testing needs.Tools that support specialized testing needs are tools that assist with performing dynamic testing activities related to specific domains or technologies3. Examples of tools that support specialized testing needs are:

Tools for security testing

Tools for performance testing

Tools for accessibility testing

The correct answer is C, as it describes a benefit of test automation.Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions1.Test automation can have many benefits, such as reduction in repetitive manual work1.This can improve the efficiency and effectiveness of testing by saving time, effort, and resources1. Option A is incorrect, as it does not describe a benefit of test automation, but a factor that influences the selection of test automation tools.Availability of the test automation tool vendor is a factor that affects the availability and support of the tool, which may affect the success of test automation1. Option B is incorrect, as it does not describe a benefit of test automation, but a misconception.Negligible effort to maintain the test assets generated by the tool is not true, as test automation requires regular maintenance and update of the test scripts, data, and expected results to cope with changes in the software under test1. Option D is incorrect, as it does not describe a benefit of test automation, but a drawback.More subjective assessment is not a benefit, as test automation may introduce bias and errors in the test results due to human factors such as lack of skills, knowledge, or experience1.

Reference:1, Section 2.10

In the context of software testing, the correct sequence of events typically starts with amistake, which is a human error made during the software development process. This mistake can lead to afaultin the code, which is a defect or bug that exists in the software. If this fault is executed, it may cause afailure, which is an instance where the software does not perform its intended function.

Traceability between the test basis and test work products means that there is a clear and documented relationship between the requirements, design, and other sources of test conditions, and the test cases, test procedures, and test results that are derived from them. This helps to ensure that the test work products are consistent, complete, and relevant to the test basis. One of the direct benefits of maintaining traceability is the ability to analyse the impact of changes in the test basis on the test work products, and vice versa. For example, if a requirement is changed, added, or deleted, traceability can help to identify which test cases, test procedures, and test results need to be updated, executed, or removed accordingly. Similarly, if a test result reveals a defect in the test basis, traceability can help to locate the source of the defect and determine the scope of the correction. Traceability also supports other benefits, such as measuring test coverage, reporting test progress, and evaluating test quality, but these are not direct benefits of maintaining traceability, rather they are outcomes of using traceability information for various purposes.Reference: ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 3.1.2, p.23-241; ISTQB Glossary v4.0, p.672

Maintenance testing is triggered bychangesto the software or its environment, or byretirementof the software or its environment1. Therefore, the events that would represent triggers for maintenance testing are:

Upgrading the production system's database for the latest Oracle release (a change to the environment)

Retirement of a live application that no longer has business benefit (a retirement of the software)

The other events are not triggers for maintenance testing, because they are either related to the development or testing process, or do not involve any change or retirement of the software or its environment. They are:

Migrating tests from a spreadsheet to the new test management tool (a change to the testing process)

An urgent fix to a new application before its initial release to production (a change to the software in development)

Simplifying the requirements to make them easier to analyse and review (a change to the requirements in development)