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

2400, 1000, 2301 are test case inputs that each fall into a different equivalence partition1.Equivalence partitioning is a black box test design technique that divides the input domain of a system into partitions of equivalent data2.Each partition should contain data that is expected to be treated the same by the system2.Therefore, only one test case input from each partition is needed to test the system's behaviour2. In this question, the input domain of the system is the time of travel, which can be divided into three partitions based on the fare rules:

Peak-time tariff: This partition contains all the times between 0600 and 1000 (inclusive), which are subject to a higher fare.

Off-peak tariff: This partition contains all the times between 1001 and 2259 (inclusive), which are subject to a lower fare.

No service: This partition contains all the times between 2300 and 0559 (inclusive), which are not valid for travel.

Therefore, to test the system's behaviour for each partition, we need to choose one test case input from each partition. Among the options given in this question, only D contains one test case input from each partition. 2400 belongs to the no service partition, 1000 belongs to the peak-time tariff partition, and 2301 belongs to the off-peak tariff partition. Therefore, D is the correct answer.

Boundary value analysis and decision table testing are the best choice of one black box technique and one white box technique for test case design2.A black box technique is a technique that uses the external behaviour or specification of a system as a test basis to derive test cases without referring to its internal structure or logic2.A white box technique is a technique that uses the internal structure or logic of a system as a test basis to derive test cases and measure test coverage2. In this question, the system has complex business rules and many branches in the structure of its code components. Therefore, we need to choose a black box technique that can handle complex business rules and a white box technique that can cover many branches.

Boundary value analysis is a black box technique that tests the values at or near the boundaries of an equivalence partition2.Boundary value analysis can handle complex business rules by identifying the boundary conditions that may cause errors or exceptions in the system's behaviour2.

Decision table testing is a white box technique that tests all possible combinations of conditions and actions in a decision logic2.Decision table testing can cover many branches by creating a table that shows how each condition affects each action and then deriving test cases from each row of the table2.

Therefore, boundary value analysis and decision table testing are the best choice of one black box technique and one white box technique for test case design.

Equivalence partitioning is a black box test design technique2.A black box technique is a technique that uses the external behaviour or specification of a system as a test basis to derive test cases without referring to its internal structure or logic2.Equivalence partitioning is a technique that divides the input domain of a system into partitions of equivalent data2.Each partition should contain data that is expected to be treated the same by the system2.Therefore, only one test case input from each partition is needed to test the system's behaviour2. Therefore, equivalence partitioning is a black box test design technique.

Statement testing is a white box test technique2.A white box technique is a technique that uses the internal structure or logic of a system as a test basis to derive test cases and measure test coverage2.Statement testing is a technique that uses executable statements in the source code as a test basis to measure the coverage achieved by a test suite2.A statement is an instruction or command that performs an action or calculation in the source code2.Statement testing requires every statement in the source code to be executed at least once by a test suite2. Therefore, statement testing is a white box test technique.

The testability of requirements is evaluated during the Test Analysis and Design stage of the fundamental test process3. The fundamental test process consists of five main activities:

Test Planning and Control: This activity involves defining the scope, objectives, approach, and resources for testing, as well as monitoring and controlling the test progress and results3.

Test Analysis and Design: This activity involves analyzing the test basis (such as requirements, design, etc.) and designing the test cases, procedures, and environment3.The testability of requirements is evaluated during this activity, as it involves checking the clarity, completeness, consistency, and testability of the requirements3.

Test Implementation and Execution: This activity involves implementing the test cases and procedures, preparing the test environment and data, executing the test cases, and logging the test results and incidents3.

Evaluating Exit Criteria and Reporting: This activity involves evaluating the test results against the exit criteria (such as coverage, defect rate, etc.) and reporting the test status and outcomes to the stakeholders3.

Test Closure Activities: This activity involves finalizing the test documentation, archiving the test artifacts, evaluating the test process and lessons learned, and releasing the test resources

A test procedure specification is a document that gives the precise steps needed in order to execute a test2.A test procedure specification defines how to run each test case or group of test cases in a specific order, including any preconditions, postconditions, inputs, outputs, actions, verifications, and expected results2.A test procedure specification can also include information about the test environment, tools, data, roles, responsibilities, risks, etc2. Therefore, a test procedure specification is a document that gives the precise steps needed in order to execute a test.

Preventing defects from being introduced into the code is not a valid objective of testing, because testing can only detect defects that are already present in the code, not prevent them from happening. Testing can help prevent future defects by providing feedback to developers and other stakeholders, but it cannot guarantee that no defects will be introduced.Preventing defects is more related to quality assurance activities, such as reviews, inspections, and standards12.

Having an independent test function in an organisation can improve defect finding during reviews and testing, because independent testers can provide a different perspective and have less bias than developers or other stakeholders.Independent testers can also focus on testing activities without being influenced by development pressures or deadlines12. The other options are not valid reasons for having an independent test function. Option B is more related to code reviews, which can be done by developers themselves or by peers. Option C is not beneficial, because communication between developers and testers is essential for effective testing and defect resolution.Option D is not directly related to the test function, but to the test management and reporting processes12.

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.