Baseline Management
Skill Purpose: Maintain baselines for regression, performance, and snapshot tests to detect meaningful changes.
Core Skill Pattern
Objective: Define and manage trusted baselines for comparison and alerting.
Universal Pattern:
- •Establish baseline sources and owners
- •Version baselines with code changes
- •Review baseline updates via PR
- •Automate comparisons in CI
- •Archive historical baselines
Key Decisions (Project-Specific):
- •Which metrics require baselines
- •Approval process for baseline updates
- •Storage and retention strategy
Project-Specific Implementation Notes
Customize per project:
- •Keep baselines deterministic and reproducible
- •Separate performance and UI snapshot baselines
Example Implementation (Snapshot Testing)
code
# Update snapshots (only when approved) npm test -- -u
Best Practices
- •Require review for baseline updates
- •Store baselines in version control
- •Document the rationale for changes
- •Keep baselines small and focused
- •Avoid updating baselines to hide regressions
Stop Conditions
STOP and escalate if:
- •Baseline changes are unreviewed
- •Baselines are non-deterministic
- •Comparison results are not reproducible
Skill Version: 1.0.0