ISTQB CTAL-TTA Practice Test - Questions Answers, Page 12

The correct description of continuous testing is that each new build of the system triggers a pre-defined set of tests to be executed automatically. This approach ensures that any changes or additions to the system are immediately validated, helping to catch issues early and streamline the development process .

The statement 'Test suite coverage can be increased without the need for refactoring' is accurate because test suite coverage refers to the extent to which the test cases cover the software under test. This coverage can be enhanced by adding new tests that address areas not previously covered, without necessarily modifying the existing test structures or setups. Refactoring is often related to improving the internal design of the tests for better maintainability or performance but does not inherently affect the coverage directly .

In software testing, especially within contexts like nuclear power plants, achieving a 'highly recommended' level of coverage often requires strategic test case selection to verify all logical conditions are accurately assessed. For the condition 'If ((A > B) or (C > D)) and (E = F) then print A', the critical tests involve evaluating the boolean logic.

Test Case Analysis: Test Set 1 is selected because it should ideally include scenarios where:

Both conditions (A > B) and (C > D) are true, and (E = F) is true to ensure the print statement executes.

One of the conditions (A > B) or (C > D) is false while the other is true, combined with (E = F) being true, to test the OR logic.

Both conditions (A > B) and (C > D) are false with (E = F) being true, which should not trigger the print statement, testing the AND logic.

Condition where (E != F), irrespective of other conditions, to confirm that the print statement does not execute.

Testing that focuses on confirming that data backup tapes can be retrieved and loaded within specified service levels is classified as Continuity Testing. This type of testing ensures that business processes can continue after a disruption, such as data loss or system failure.

Installability testing is usually conducted during the System Testing stage of the SDLC. It typically includes testing the installation process of the software to verify that it installs correctly across various systems and configurations. This type of testing often overlaps with functionality testing to ensure all functions are available post-installation, and usability testing to ensure that the installation process is intuitive and user-friendly.

Story Mapping is an effective requirements engineering technique used in Agile environments to provide a visual representation of the system. It helps in understanding the 'overall' story and functional flow by mapping user stories along a timeline or process steps, laying them out in a two-dimensional structure that represents the product backlog. This technique is particularly useful for visualizing the scope of large features or entire systems, making it easier to plan releases and improve understanding among the team .

The BDD scenario written in Gherkin format that correctly applies to the given user story is:

Given that a customer has booked a flight with Alpha Airways When that customer enters the correct surname and flight number for this reservation Then the booking details for that flight are displayed ELSE an appropriate error message is presented

This scenario directly aligns with the user story by specifying the necessary conditions and outcomes for accessing and updating flight reservation details, ensuring that the scenario correctly captures the functionality described in the user story .

Table 2 correctly represents the calculation of tax to pay and net salary for employees of a Payroll system, including accurate representation of tax rates as percentages (not whole numbers), and the correct year-to-date accumulation of salary paid, which aligns with the payroll system's operations as described. It accounts for the logical incrementation of cumulative figures and uses percentage representations for tax rates, which is a standard approach in payroll calculations .

The statement that is true about test approaches is that in a Model-based test approach, tests can be created automatically. This is confirmed by the understanding that model-based testing involves generating test cases directly from a model that describes the system functions, behavior, or both, which supports automatic test creation.