Automatic Merge Request Analysis
ReGrade replays recorded production traffic against every merge request, automatically surfacing behavioral and performance differences before code reaches production.
The Merge Request Pipeline
- CI Pipeline runs tests on stable code in master branch (ReGrade records all traffic)
- master branch
- feature branch
- Developer (AI/Human) writes new feature and creates a merge request in CI pipeline
- ReGrade replays stable code's recorded traffic to the new feature build
- ReGrade records any behavior or performance differences
- CI pipeline has AI agent ask ReGrade MCP for differences and then tags as unintended or intended
- Developer (AI/Human) uses difference summary to deny or approve merge request
- merge feature into master branch
Benefits
Faster review
Automated traffic replay surfaces behavioral changes instantly, so reviewers spend time on real issues instead of hunting for regressions.
Auditable artifacts
Every merge request gets a detailed diff of behavioral and performance changes, creating a permanent audit trail.
More insight than pass/fail
Go beyond binary test results — see exactly which API responses changed, how performance shifted, and what the impact is.
Root cause information
ReGrade doesn't just flag differences — it provides the context needed to understand why behavior changed.