Maintenance testing is?
-
updating tests when the software has changed
-
testing a released system that has been changed
-
testing by users to ensure that the system meets a business need
-
testing to maintain business advantage
Maintenance testing involves testing a system that has already been released and is operational, after changes or modifications have been made. It ensures that updates, patches, or enhancements haven't introduced defects and that the system continues to function correctly in its production environment.
Maintenance testing is testing performed on an already-released, live system after it has been changed — correct per ISTQB definitions. Changes triggering maintenance testing include bug fixes, planned enhancements, migration to new environments, or retirement of parts of the system; the key distinguishing factor is that the system is already in production/live use when the change and its testing happen. 'Updating tests when software has changed' describes test maintenance (updating test assets), not maintenance testing itself. 'Testing by users to confirm a business need is met' describes acceptance testing (specifically UAT), and 'testing to maintain business advantage' isn't a recognized testing type at all — it's a distractor with no formal meaning in the testing glossary.