ISTQB CTFL-Foundation Exam Dumps

Test case 1 exercises the decision outcomes True, False, False

Test case 2 exercises the decision outcomes False, True, False

This leaves the True outcome of decision 3 not exercised.

Of the 6 possible decision outcomes, 5 have been exercised, so the decision coverage is 5/6 (about 83%).

Maintenance testing is conducted on the software after it has been delivered to address any issues or changes required due to defects, environment changes, or new requirements. The ISTQB syllabus explains that maintenance testing typically involves impact analysis to determine the extent of regression testing required, thus optimizing the testing effort and focusing on affected areas.

The amount of testing that is considered enough depends on various factors, including the level of risk associated with the application, industry standards, contractual obligations, and specific requirements. It is a risk-based decision that balances the need for thorough testing with time and resource constraints. Reference: ISTQB CTFL Syllabus V4.0, Section 5.2.2.

Based on the given flow graph and the test cases provided:

Test Case 1 covers the path P Q R U.

Test Case 2 covers the path P Q S V.

Test Case 3 covers the path P Q S W X.

Test Case 4 covers the path P Q S W Y.

All decision points (P, Q, R, S, W) are covered at least once, ensuring 100% decision coverage. However, not all statements (T) are covered, as there is no test case that covers the path leading to statement T.

White box testing techniques, also known as structure-based techniques, focus on the internal structure of the software. Decision testing (C) is a white box technique that involves creating test cases to execute specific decision points in the code, such as conditional statements. This ensures that all possible paths through the code are tested, helping to identify defects related to the control flow of the application. Other techniques listed, such as use case testing and state transition testing, are black box techniques that focus on the software's functionality from the user's perspective.