Free iSQI CTFL_Syll2018 Practice Exam with Questions & Answers | Set: 9

Statement coverage is not a black box technique, because it requires knowledge of the internal structure of the code. Black box techniques are based on the external behavior and specification of the software, without looking at the code. Equivalence partitioning, state transition testing, and boundary value analysis are all examples of black box techniques12

To be based on an analysis of the structure of the component or system. White box testing techniques are based on the internal structure and code of the system, not on its specifications or functionality. White box testing techniques include statement coverage, decision coverage, branch coverage, path coverage, etc. White box testing techniques are usually performed at lower levels of testing, such as unit testing or component testing. A detailed explanation of white box testing techniques can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 68-74.

Functional and structural tests are alternative test types that may be used separately or together at B. All test levels. Functional testing is a type of testing that verifies the functionality of the system or component under test against its requirements or specifications. Functional testing focuses on what the system or component does, not how it does it. Structural testing is a type of testing that verifies the structure or code of the system or component under test. Structural testing focuses on how the system or component does it, not what it does. Functional and structural testing can be used separately or together at any test level, such as unit testing, integration testing, system testing, acceptance testing, etc. Functional and structural testing can complement each other by providing different perspectives and coverage of the system or component under test. A detailed explanation of functional and structural testing can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 25-26.

 Equivalence partitioning is a technique that divides the input domain of a system into partitions or classes that are expected to behave similarly or produce similar outputs2. A test case can cover one value from each partition, as it is assumed that all values in the same partition are equivalent for testing purposes2. In this question, the groups of numbers fall into different equivalence classes based on the amount of customs duty to be paid, as shown below:

Group

Equivalence Classes

$20,000 $20,001 $30,001

No duty (up to $2,000), 10% duty ($2,001-$10,000), 12% duty ($10,001-$30,000), 17% duty (above $30,000)

$2,000 $2,001 $10,000

No duty (up to $2,000), 10% duty ($2,001-$10,000), 12% duty ($10,001-$30,000)

$2,000 $8,000 $20,000

No duty (up to $2,000), 10% duty ($2,001-$10,000), 12% duty ($10,001-$30,000)

$1,500 $2,000 $10,000

No duty (up to $2,000), 10% duty ($2,001-$10,000)

A limitation in the use of static analysis tools is C. Static analysis tools always generate large numbers of warning messages when applied to new code, even if the code meets coding standards. Static analysis tools are tools that analyze the code or other software artifacts without executing them, and report any defects, errors, vulnerabilities, or violations of coding standards or conventions. Static analysis tools can help to improve the quality and maintainability of the code or other software artifacts. However, static analysis tools also have some limitations, such as generating large numbers of warning messages when applied to new code, even if the code meets coding standards or conventions. This can make it difficult for developers or testers to identify and prioritize the most important or critical issues to fix or address. A detailed explanation of static analysis tools can be found in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, pages 109-1101.

Testing is the process of evaluating a software product by learning about it through exploration and experimentation, which includes running tests, observing outcomes, making inferences, and creating and refining test ideas. Testing has many objectives, such as finding defects, providing information, improving quality, reducing risks, etc. One of the objectives of testing is preventing defects, which means avoiding or minimizing the occurrence of defects in the software product by applying good practices and techniques throughout the software development life cycle. Preventing defects can help to save time, cost, and effort in testing and development, and improve customer satisfaction and confidence. A detailed explanation of testing objectives can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 7-8.

Finding defects, gaining confidence about the level of quality and providing information, and preventing defects are all valid test objectives according to the ISTQB Foundation Level syllabus. Debugging the code is not a test objective, because debugging is the process of finding and fixing defects, which is done by developers, not testers3

Testing support tools are software tools that assist testers in performing testing activities, such as test management, test design, test execution, test evaluation, and defect management1. According to the ISTQB syllabus, some typical targets of testing support tools are to automate activities that require significant resources when done manually, automate activities that cannot be executed manually, and automate repetitive tasks1. Automating repetitive inspections is not a typical target of testing support tools, as inspections are static testing techniques that involve human review and analysis of software artifacts1.

 These are some of the factors that should be considered to determine whether enough testing has been performed. The exit criteria define the specific goals and requirements for testing completion. The budget limits the resources and time available for testing. The product’s risk profile indicates the areas of highest priority and impact for testing. Sufficient details of the system status allow decisions on whether further testing is needed or not. The other options are not relevant factors for determining enough testing.

The main reason for using a pilot project to introduce a testing tool into an organization is C. To assess whether the tool will be cost-effective. A pilot project is a small-scale trial or experiment that is used to evaluate the feasibility, benefits, risks, and challenges of introducing a testing tool into an organization. A pilot project can help to assess whether the tool will be cost-effective, by comparing the costs of acquiring, deploying, using, and maintaining the tool with the benefits of using the tool, such as increased efficiency, effectiveness, quality, etc. A pilot project can also help to identify any technical, organizational, or human factors that may affect the successful adoption of the tool, and plan for any necessary actions or changes to address them. A detailed explanation of pilot projects can be found in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, pages 115-1161.