2.3. Maintenance Testing Flashcards
What can maintenance be?
Corrective, adaptive to changes in environment or improve performance or maintainability.
What can maintenance involve?
Planned releases/deployments and unplanned releases/deployments (hot fixes).
What may impact analysis be done before?
A change is made.
What does impact analysis help decide?
If change should be made based on potential consequences in other areas.
What does testing changes include?
Evaluating success of implementation and checking for possible regressions in parts that remain unchanged.
On what does scope of maintenance testing typically depend?
Degree of risk, size of existing system, size of change.
How can triggers for maintenance and maintenance testing be classified?
Modifications (planned enhancements, corrective changes or hot fixes), Upgrades or migrations (from one platform to another), Retirement (when application reaches end of life).
What can upgrades or migrations require?
Tests associated with new environment and changed software.
What can upgrades or migrations require?
Tests of data conversion when data from another application is migrated into system.
What can retirement require?
Testing data archiving if long data retention periods are required.
What may also be needed after archiving?
Testing restore and retrieval procedures if certain data is required during archiving period.
