What is the difference between re-testing and regression testing?

Re-testing specifically involves running a test case again to confirm that a defect has been fixed. It is a focused effort that targets a particular defect that was identified and resolved, ensuring that the specific functionality works as intended after the fix. This is typically performed after developers address the reported issues to validate that the changes have resolved the problem without reintroducing it.

Regression testing, on the other hand, is broader in scope. It checks that recent changes in the codebase (such as bug fixes, enhancements, or new features) have not inadvertently affected the existing functionality of the software. This testing aims to catch any unexpected side effects that could arise from code changes, ensuring that the overall system remains stable and behaves as expected even after modifications.

Therefore, stating that re-testing is centered around running the test again specifically to confirm a bug fix, while regression testing is concerned with identifying any unforeseen consequences of changes, accurately delineates their distinct purposes and practices.