Triggers for Maintenance Testing (Exam D – Question 14)
1. Introduction
In the ISTQB Foundation Level syllabus, maintenance testing is performed after a system has been deployed to ensure that changes do not introduce unintended side effects.
This question checks whether you understand what situations actually trigger maintenance testing.
ISTQB에서 유지보수 테스트(Maintenance testing)는 시스템이 운영 환경에 배포된 이후 변경 사항으로 인한 영향을 확인하기 위해 수행됩니다.
이 문제는 유지보수 테스트를 유발하는 트리거를 정확히 알고 있는지 묻습니다.
2. Practice Question
❓ Question
Which of the following is MOST likely to be a trigger that leads to maintenance testing of a currency exchange system?
- a) The developers reported that changing the currency exchange system was difficult and the testers decided to check if this was true
- b) The refund option of the currency exchange system was removed as it did not always repay the correct amount to customers
- c) The agile team has started developing a user story that adds a new customer loyalty feature to the currency exchange system
- d) The language support option of the currency exchange system was used to enable both English and local language currency transactions
✅ Correct Answer: b)
3. Explanation
✔ b) Removal of the refund option — Correct
A system modification is one of the main triggers for maintenance testing.
Removing the refund option is a fix to address incorrect behavior. Such a change requires maintenance testing to verify:
- The fix works as intended
- No unintended side effects were introduced
유지보수 테스트의 대표적인 트리거는 시스템 수정(System modification)입니다.
환불 옵션 제거는 잘못된 동작을 수정하기 위한 변경이므로 유지보수 테스트를 수행해야 합니다.
❌ a) Checking how easy the system is to change — Incorrect
Checking how easy it is to modify the system relates to maintainability testing, which is a type of non-functional testing.
It is not a trigger for maintenance testing.
시스템 변경의 용이성을 확인하는 것은 유지보수성(Maintainability) 테스트로,
유지보수 테스트를 유발하는 트리거가 아닙니다.
❌ c) Developing a new user story — Incorrect
Adding a new feature under development results in testing of that feature and regression testing.
This is not maintenance testing.
새로운 사용자 스토리 개발은 기능 테스트 및 회귀 테스트로 이어지며,
유지보수 테스트 상황은 아닙니다.
❌ d) Enabling language support — Incorrect
Reconfiguration without modifying the system, changing the operational environment, or retiring the system does not trigger maintenance testing.
단순 설정 변경은 시스템 수정, 운영 환경 변경, 시스템 종료에 해당하지 않으므로
유지보수 테스트 트리거가 아닙니다.
4. Summary Table
| Option | Situation | Maintenance Testing Trigger? | 구분 |
|---|---|---|---|
| a | Assess ease of change | ✖ No | 유지보수성 테스트 |
| b | System fix/modification | ✔ Yes | 수정 트리거 |
| c | New feature development | ✖ No | 회귀 테스트 |
| d | System reconfiguration | ✖ No | 설정 변경 |
5. Final Takeaway
For the ISTQB exam, remember the three main triggers for maintenance testing:
System modification, change in the operational environment, or system retirement.
시험 대비 핵심 문장입니다.
유지보수 테스트의 트리거는 시스템 수정, 운영 환경 변경, 시스템 종료이다.
Related: More ISTQB Posts | Next Question