Overview
Regression testing ensures that recent changes to the codebase—such as new features, bug fixes, or refactoring—haven’t negatively affected existing functionality. It plays a crucial role in maintaining software stability as the product evolves.
Purpose
- Detect unintended side effects from code changes
- Validate that existing features still work correctly
- Prevent production issues caused by regressions
Types of Regression Tests
- Unit Regression: Test impacted units in isolation
- Partial Regression: Test modified modules in context
- Complete Regression: Re-test the full application
When to Run Regression Tests
- After new feature development
- After bug fixes or performance improvements
- Before major releases
- As part of CI/CD pipelines
Related Context
