CTAL-TTA Exam Dumps : Certified Tester Advanced Level Technical Test Analyst

Statements about Maintainability Testing:

A. It should start as soon as the draft design documents are available for review.

True. Maintainability testing can begin early in the development lifecycle, starting with reviews of design documents to ensure that maintainability concerns are addressed from the outset.

B. An application can be considered maintainable when static analysis and code review defects have been fixed.

False. While fixing defects identified by static analysis and code reviews improves maintainability, other factors such as documentation, ease of making changes, and regression testing must also be considered.

C. It tests the regression impact of software or environmental changes to an operational system.

False. This describes regression testing more than maintainability testing, which focuses on the ease of modifying the system and maintaining its performance.

D. It can be performed during Operational Acceptance Testing by multiple departments.

True. Maintainability testing can be part of operational acceptance testing (OAT), where different departments ensure that the system can be maintained and operated effectively.

E. It can be performed during User Acceptance Testing to ensure business processes can be maintained.

False. User acceptance testing (UAT) focuses on verifying that the system meets business requirements and user needs, not specifically on maintainability.

Correct Answer:

B. a and d

References:

The ISTQB CTAL-TTA syllabus and standard testing practices emphasize the importance of maintainability testing early in the lifecycle and its role in operational acceptance testing.

Sources:

ISTQB-CTAL-TTA Syllabus

General knowledge on maintainability testing practices.

Once existing test cases have been identified for refactoring, the next step is typically to make changes to the internal structure of these tests to improve their maintainability. This involves revising the code or scripts to make them cleaner, more efficient, and easier to understand, which helps in maintaining them over time as the software evolves. This process may also involve updating test data or dependencies to ensure that the tests remain robust and reliable .

The control flow graph provided illustrates the decision points for an airline's upgrade and boarding process. Decision coverage is a measure of the percentage of decision points executed during testing:

Test 1 covers the decision points: Gold card? (Yes) and Business full? (No).

Test 2 covers: Gold card? (No) and Economy full? (No).

Test 3 covers the decision that leads to being bumped from the flight, which is Economy full? (Yes) and Business full? (Yes).

From the given tests, the decision points for Gold card? (No) and Business full? (No) are not tested, leaving us with 4 out of 6 decision points covered, which is approximately 67% decision coverage.