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.
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.