CTAL-TTA Leak Questions

To achieve 100% decision coverage with the minimum number of test cases, we need to ensure that every branch of the decision is taken at least once. For the code provided:

• The first condition(a>b)is true for the first two test cases and false for the third.
• The second condition(b>c)is true for the first test case, false for the second, and does not matter for the third since the first condition is false.

Therefore, with these three test cases, we cover all possible outcomes of the decision, ensuring 100% decision coverage.

In the context of an internet banking project where reliability and maintainability are emphasized, a key factor for maintainability is the modularity of the system. Implementing the user interface independently from other software modules (answer B) can significantly enhance maintainability. This is because it allows changes to be made to the user interface withoutimpacting the underlying business logic or data access layers, making the system more adaptable to change. This kind of separation of concerns is a recognized best practice in software design for maintainability. The other options (A, C, and D) relate more to reliability and security aspects than to maintainability.

Tools that support component testing and the build process are designed to provide a controlled environment where individual units or components of the software can be tested in isolation. This is typically done using stubs, which simulate the behavior of missing components, and drivers, which simulate the behavior of a user or calling program. This isolated environment is essential for unit testing because it allows testers to find defects within the boundaries of a single component before integrating it into the larger system.

In the context of API testing, the defect types generally found are related to the specific interactions with the API, such as issues with data formatting, handling, validation, and the sequencing or timing of API calls. Architectural structural complexity is not typically a defect that would be identified at the API testing level. API tests are concerned with the interface and immediate integration points, not the overarching system architecture, which would be more relevant to design or system-level testing.