Reports and impact
Reports help you answer questions like "what changed?", "which cases would be affected?", and "is this change safe to move forward?" — without reading every line of content.
Questions it answers
- What changed between two versions (or workspaces) of the project?
- Which test cases would the current change affect?
- Which problems (warnings, diagnostics) appear most often?
- Did the current change improve or hurt the project's score?
What the screen shows
- Snapshot comparison — side-by-side view of what changed.
- Case impact — which test cases would feel the change.
- Recurring diagnostics — problems repeating across the project.
- Workspace impact calculation — aggregated view before publishing.
Before you start
- An active project.
- Enough workspaces or versions to compare.
- Permission to view the project.
Using it day-to-day
- Before opening a large review, use the impact report to anticipate reviewer questions.
- After publishing, compare the new version with the previous one to document changes for the team.
- Use recurring diagnostics to find high-leverage refactors — a problem that appears in dozens of places, fixed once, improves the whole project.
Limitations
- If the project has few workspaces or versions, comparisons are limited.
- Impact quality depends on having good test cases recorded.