Maintenance Testing
Maintenance testing verifies that changes made during software maintenance work correctly and have not introduced unintended side effects.
“Testing the changes to an operational system or the impact of a changed environment to an operational system.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Maintenance Testing?
It typically includes confirmation testing of fixes and regression testing of existing functionality affected by maintenance changes.
Change validation: Confirms implemented changes behave correctly.
Regression focus: Existing features are retested after modifications.
Risk reduction: Helps prevent new defects from reaching production.
Real World Example
A regulated product team is preparing a release where Maintenance testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Maintenance testing as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Maintenance testing and similar ideas.
The page becomes useful in practice because Maintenance testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Maintenance testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Maintenance testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Maintenance Testing. Test your understanding with topic-specific questions in our Mock Exams.