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.

For a Medium risk mission- or safety-critical system, the best testing approach includes a combination of automated tests, exploratory tests, and manual black-box tests. Option B is the most comprehensive, advocating for automated tests to ensure reliability and repeatability, highly recommending exploratory tests to cover unforeseen scenarios, and recommending manual black-box tests to cover standard use cases. This multifaceted approach ensures thorough testing coverage essential for medium risk, safety-critical systems​​.

Service virtualization in the context of developing an e-shop application with an external payment gateway (still under development) offers significant benefits. It allows for realistic testing of the System Under Test (SUT) by simulating the behavior of the still-developing payment gateway, thus enabling testing to proceed without the actual service being available. Additionally, it simplifies the test environment by reducing the complexities associated with integrating and maintaining a live external service during development and testing phases .