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

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.

To achieve 100% statement coverage, we need to execute every statement in the code at least once. To achieve 100% decision coverage, we need to execute every possible outcome of every decision in the code at least once. In this case, we can use the following test cases to cover both statement and decision coverage:

A = 5, B = 4, C = 3, D = 2, E = 1

A = 1, B = 2, C = 3, D = 4, E = 5

A = 3, B = 4, C = 5, D = 2, E = 1

A = 3, B = 2, C = 1, D = 4, E = 5

These four test cases will cover all the statements and all the possible outcomes of the decisions in the code. Therefore, the minimum number of test cases required to achieve both statement and decision coverage is four.

To achieve 100% statement coverage, we need to execute every statement in the code at least once. To achieve 100% decision coverage, we need to execute every possible outcome of every decision in the code at least once. In this case, we can use the following test cases to cover both statement and decision coverage:

A = true, B = true

A = false, B = false

These two test cases will cover all the statements and all the possible outcomes of the decisions in the code. Therefore, the minimum number of test cases required to achieve both statement and decision coverage is two.

Use case testing is a technique that uses scenarios based on use cases to test the functionality and usability of a system from the user's perspective. A use case is a description of how a system interacts with one or more actors (users or other systems) to achieve a specific goal. A typical benefit of use case testing is finding failures in the business process flows, which highlight system use in the real world. This is because use case testing focuses on how the system is used by different actors in different situations, rather than on individual components or features of the system.

The statement that environmental conditions only affect the hardware - not the software is not a good explanation why software failures can be caused by environmental conditions. Environmental conditions can affect both the hardware and the software, as they can influence the performance, reliability, and functionality of the system. For example, factors like magnetism, radiation, pollution, heat, humidity, vibration, etc. can affect electronic devices and the embedded software that runs on them. Software failures caused by environmental conditions can have serious consequences, especially for safety-critical systems.

Reference:Certified Tester Foundation Level Syllabus, Section 1.2.2

Non-functional testing is a type of testing that focuses on the quality attributes of the system or its components, such as performance, reliability, usability, security, etc. Non-functional testing can be done at any test level, depending on the test objectives and scope. In this case, the test types that are non-functional tests are:

Acceptance test: A test level that focuses on verifying whether the system meets the user's needs and expectations, and whether it is acceptable for delivery or deployment.

Stress test: A type of performance testing that evaluates the behavior of the system under extreme or abnormal conditions, such as high load, limited resources, or concurrent access.

Reliability test: A type of testing that evaluates the ability of the system or its components to perform their required functions under stated conditions for a specified period of time.

Therefore, statements I, II,I, and V are correct.

Test control is a test management activity that involves making decisions based on information from test monitoring and test progress reporting. Test control activities include:

Re-prioritizing tests because of time pressure

Changing the test schedule due to availability of a test environment

Setting entry and exit criteria for test levels or test activities

Initiating corrective actions to resolve deviations from the test plan

Writing test suspension and resumption criteria in the test plan is not a test control activity, but rather a test planning activity. Test suspension and resumption criteria are used to define when to stop and resume testing in case of unforeseen events or issues that affect the test execution.

The statement that use cases are normally derived from decision tables is not true. Decision tables are a technique to represent complex logical conditions in a tabular form, where each column represents a possible combination of conditions and actions. Use cases are a technique to describe how a system interacts with one or more actors (users or other systems) to achieve a specific goal. Use cases are not derived from decision tables, but from the requirements and the user's perspective of the system.

Defect density is a metric that measures the number of defects identified in the system under test divided by the size of the system. The size of the system can be measured in different ways, such as lines of code, function points, or modules. Defect density can be used to compare the quality of different systems or different versions of the same system.