As an ISTQB tester, it is important to understand that maintenance testing is critical to software maintenance. It involves testing the changes made to the software, either to fix defects or to add new functionality.
Ensure they have not introduced any new defects or caused any regressions in the existing functionality. Maintenance testing can involve multiple test levels and types depending on the scope of the changes.
Scope for Maintenance testing
The scope of maintenance testing is determined by several factors, including the degree of risk associated with the change, the size of the existing system, and the size of the change. For example, the difference is significant and affects multiple components or systems. In that case, it may require testing at the system or acceptance level using a combination of functional and non-functional test types.
Scope for Maintenance testing(contd.)
On the other hand, if the change is minor and affects only a small component of the system, it may only require testing at the branch or integration level using white-box or change-related test types. Understanding the scope of maintenance testing is important in determining the appropriate testing level and test types for each maintenance release.
Need of Maintenance testing
Maintenance testing is important for ensuring that any changes made to a software system, whether planned or unplanned, do not negatively impact the system's performance, security, or other non-functional qualities.
Triggers of Maintenance testing
There are various maintenance triggers, such as software modifications, migrations to new platforms, and retirements of old systems. In the case of Internet of Things systems, maintenance testing is also important for ensuring that new hardware devices and software services are integrated properly, and that security risks are minimized, especially when personal data is involved.