ISTQB – Foundation 2.4 – Maintenance testing

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.

  1. Planned Enhancements ex: 1.1, 1.2, 1.3 needs regression
  2. COTS Software – Commercial of the shelf – third party software added as new feature integrated with the existing software
  3. Migration- One platform to another-> windows to Linux
  4. 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

  1. Specs ae missing
  2. Test cases are out of date
  3. Bi-directional traceability between tests are not updates
  4. Tool support is weak (needs automation)
  5. The people involved do not have domain or system knowledge
  6. Insufficient attention has bee paid to the software’s maintainability during developers.