| name | regression-test |
| description | Run regression testing suite to verify existing functionality still works after changes |
Regression Testing Skill
Validates that existing functionality continues to work correctly after code changes, deployments, or dependency updates.
When to Use
- After code deployments
- After dependency updates
- Before releases
- After bug fixes
- After feature additions
- Periodic health checks
Capabilities
- Baseline comparison - Compare current behavior to known good state
- Critical path testing - Focus on essential functionality
- Change impact analysis - Identify areas affected by changes
- Automated execution - Run systematic regression tests
- Diff reporting - Highlight what changed from baseline
Workflow
Phase 1: Scope Definition
Determine regression scope based on changes:
- Full - Test all critical paths (major releases, risky changes)
- Targeted - Focus on areas affected by specific changes
- Smoke - Quick validation of core functionality (daily builds)
Phase 2: Baseline Identification
Establish expected behavior:
- Review previous test results as baseline
- Document expected responses and states
- Identify key acceptance criteria
- Note known issues to exclude
Phase 3: Test Suite Preparation
Organize tests by priority:
P0 - Critical Path (Always Run)
- Authentication flows
- Core feature functionality
