Find as many as defects possible after some changes or updates, upgrades, migration etc..
once te ptroject is released there are some timeline for theenext rls- so small updates are made in meanwhile- so maintenance tesitng is done during those mini- releases.
Lots of regression is made during these.
- Planned Enhancements ex: 1.1, 1.2, 1.3 needs regression
- COTS Software – Commercial of the shelf – third party software added as new feature integrated with the existing software
- Migration- One platform to another-> windows to Linux
- Retired- such as application reaches the end of its life ex: WinX- window sand linux embedded
In all the above cases regression is made!
IMPACT ANALYSIS
- Impact analysis is to check whether the change should be made or not, based ont he potential consequences in other areas of the system
Impact analysis is tough if
- Specs ae missing
- Test cases are out of date
- Bi-directional traceability between tests are not updates
- Tool support is weak (needs automation)
- The people involved do not have domain or system knowledge
- Insufficient attention has bee paid to the software’s maintainability during developers.