Why ReGrade®
Your suite passes and the release still breaks. Every test your team writes checks a behavior somebody predicted, and the regressions that reach customers are the ones nobody thought to predict. ReGrade compares real traffic across versions, field by field, and names what changed. Keep your existing tests and add recorded-traffic comparison where it provides useful evidence.
How ReGrade complements each testing approach
Unit & integration tests
- What it verifies
- The specific behaviors somebody wrote an assertion for.
- What it can't see
- Behavior you never thought to assert on, the unknown unknowns.
- How ReGrade complements it
- Compares entire responses field by field, so unexpected differences surface without a written assertion.
Contract testing
- What it verifies
- Agreed API schemas and consumer/provider behavior described by the contract tests.
- What it can't see
- Behavior and side effects outside the contracts that the team has specified.
- How ReGrade complements it
- Compares the actual response content across versions, field by field.
Snapshot testing
- What it verifies
- That an output still matches a previously recorded snapshot.
- What it can't see
- Outputs and execution paths outside the captured snapshots; changed snapshots still need review.
- How ReGrade complements it
- Replays recorded traffic and applies mapping rules for changing values such as tokens and timestamps. Your team reviews the rules and remaining differences.
DAST & scanners
- What it verifies
- Potential vulnerabilities found through active attack payloads and passive inspection.
- What it can't see
- Application behavior outside scanner coverage, including some business-logic and authorization failures.
- How ReGrade complements it
- Found a real password-hash leak (CVE-2023-5968) with zero prior knowledge, from traffic alone.
Manual QA
- What it verifies
- Whatever a human thinks to click through, with real judgment.
- What it can't see
- Paths the team did not exercise; repeating large test scenarios takes time.
- How ReGrade complements it
- Turns recorded requests into repeatable comparisons against reference responses.
Evidence
ReGrade compares the requests you record against a reference version. Your team reviews differences and decides what should block a release. Unrecorded paths and vulnerabilities shared by both versions still need other testing.