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

A static analysis tool can be used by developers, testers and quality assurance personnel in looking for defects prior to dynamic testing, because it can analyse the code or design of the software under test without executing it and identify errors such as syntax errors, missing declarations, undefined variables, unused variables, or unreachable code . The other options are not tools that can be used by developers, testers and quality assurance personnel in looking for defects prior to dynamic testing. Option B is not a tool that can be used for this purpose, because a modeling tool is used to create graphical or textual representations of the software under test, such as state diagrams, data flow diagrams, or use cases . Option C is not a tool that can be used for this purpose, because a test data preparation tool is used to generate or manipulate data that are needed for executing the test cases or procedures . Option D is not a tool that can be used for this purpose, because a configuration management tool is used to manage and control the versions and changes of the software under test and the testware .

Effort estimate depends on the budget of the project is the wrong statement about estimation of the test effort, because it confuses the cause and effect relationship between effort estimate and budget. Effort estimate does not depend on the budget of the project, but rather influences it. Effort estimate is an approximation of how much time and resources are needed for testing activities based on various factors such as scope, complexity, risks, quality, etc. . Budget is the amount of money that is allocated or available for testing activities based on the effort estimate . The other options are true statements about estimation of the test effort. Option A is true, because effort estimate can be inaccurate because the quality of the product under test is not known, which affects the number and severity of defects that need to be detected and fixed . Option B is true, because once the test effort is estimated, resources can be identified and a schedule can be drawn up, which are part of test planning . Option C is true, because experience based estimation is one of the estimation techniques that relies on the judgement and expertise of testers or other stakeholders who have previous knowledge or experience with similar projects .

Provides developers with information to isolate the failure is the incident report objective that this excerpt satisfies, because it gives details about how to recreate the failure using a specific test file and location . An incident report is a document that records any event that deviates from the expected or desired behaviour of the software under test . One of its objectives is to provide developers with information to isolate the failure, which means to identify and locate the cause of the failure in the software . The other options are not incident report objectives that this excerpt satisfies. Option B is wrong, because this excerpt does not belong to an incident report, but rather to a test report. A test report is a document that summarizes the results and outcomes of testing activities . Option C is wrong, because this excerpt does not provide project managers with information on the project risks, which means to identify and assess the potential threats or uncertainties that may affect the project objectives or outcomes . Option D is wrong, because this excerpt does not provide test managers with information to report test progress, which means to measure and communicate how much of the planned testing activities have been completed or remain to be done .

A walkthrough is lead by a moderator and requires pre-meeting preparation and post meeting follow up is the statement that is not true about walkthroughs, because it describes a different type of review called inspection . A walkthrough is a type of informal review that involves the author of a document presenting it to a group of peers or stakeholders to establish a common understanding and to find possible defects . A walkthrough does not have a moderator, but rather an author who leads the review. A walkthrough does not require pre-meeting preparation or post meeting follow up, but rather relies on the author's knowledge and skills . The other options are true statements about walkthroughs. Option B is true, because a walkthrough may take the form of scenarios, dry runs and peer group review, depending on the type and purpose of the document being reviewed . Option C is true, because the purpose of a walkthrough is to establish common understanding of a document and to find possible defects in it . Option D is true, because pre-meeting preparation, documentation and distribution of results are optional for a walkthrough, as they depend on the author's discretion and preference .

The statement that use case testing is designed to find defects in the process flow is true, because use case testing is a technique that tests the end-to-end user interactions and outcomes based on use cases or scenarios that describe how the software under test should be used . Use case testing can help to find defects in the process flow, such as missing steps, incorrect sequences, or invalid transitions . The other options are not true statements about use case testing. Option A is false, because use case testing is not designed to be used by real users, but rather by professional testers who design and execute test cases based on use cases or scenarios . Option C is false, because use case testing is not designed to find defects in the data flow, but rather in the process flow. Data flow testing is a different technique that tests how data values are defined, used, and modified by the software under test . Option D is false, because use case testing is not always designed by customers or end users, but rather by testers who analyse the requirements or specifications of the software under test to identify use cases or scenarios .

Checking that at least 50% of decisions have been exercised by a test case suite is not a valid use of decision coverage, because it does not meet the minimum criterion of decision coverage, which is to exercise all possible outcomes of each decision in the software under test . Decision coverage is a technique that measures how much of the logic or branching of the software under test has been exercised by the test cases . The other options are valid uses of decision coverage. Option A is a valid use of decision coverage, because it can check that all decisions have been exercised in a single program . Option B is a valid use of decision coverage, because it can check that all decisions have been exercised in a business process . Option C is a valid use of decision coverage, because it can check that all calls from one program module to another have been made correctly .

The statement that incidents cannot be raised during development is not true, because incidents can be raised during any stage of software development life cycle where deviations from expected or desired behaviour are observed . Incidents can be raised during development, review, testing or use of a software product . The other options are true statements about incidents.

Defect clustering is the phenomenon that a small number of modules contain most of the defects detected. This principle suggests that testing should focus more on the areas where defects are more likely to occur, rather than spreading the testing effort equally across all modules. Therefore, in the next test cycle, the team should allocate more resources to test the module that had most of the critical bugs.