What is included in change-related testing?

Change-related testing primarily focuses on ensuring that modifications made to a software product do not introduce new defects and that existing functionalities remain operational after the changes. This is where retesting and regression testing come into play.

Retesting is conducted to validate that specific defects identified in earlier versions have been fixed. It involves rerunning the same tests that uncovered issues to confirm that the changes worked as intended. Regression testing, on the other hand, checks that the new code changes have not negatively affected existing features that were previously functioning correctly. Together, these tests ensure the software remains stable after changes, making them essential components of change-related testing.

While other testing types such as unit testing, performance testing, and system integration testing play critical roles in the software development lifecycle, they are not necessarily focused on the direct implications of changes. For instance, unit testing validates individual components, but it does not provide a comprehensive view of the entire system's interaction post-change. Similarly, performance testing primarily assesses the application's responsiveness and stability under load, without directly addressing the impact of recent changes. System integration testing evaluates how various components work together, but it does not specifically target the changes made.

Thus, retesting and regression testing constitute the core activities in change-related testing as they directly address