RealDiff is a new tool designed to identify runtime behavior changes in software that are not apparent through standard source code review. It operates by building two Git revisions, observing their test executions, and learning a noise baseline from multiple runs. The tool then reports the first changed behavior within each call tree.
While a source code diff shows what lines were edited, RealDiff reveals the actual impact of those edits, including effects in files that were not directly touched by the pull request. This capability is crucial for catching subtle issues, such as a refactor in one part of the codebase inadvertently altering behavior in a seemingly unrelated component.
An example provided demonstrates how a one-line change from `List.Sort` to `OrderBy` in an infrastructure helper, which alters sorting stability, can lead to different results in an unedited pricing engine. In this scenario, a discount engine returned a different value, and two out of three tests executing this code did not assert on the change, highlighting a potential bug that RealDiff would flag.
RealDiff supports six programming languages. For .NET, it requires Git, .NET 8 SDK, and PowerShell 7. Java analysis needs a JDK and a Maven/Gradle wrapper, while Node analysis requires Node.js and the package manager specified in its lockfile. A public .NET demo pull request is available for inspection.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
RealDiff is a new tool that identifies runtime behavior changes in code, even in files not directly modified by a pull request, by comparing test execution between two Git revisions. This helps developers catch subtle behavioral shifts that traditional source code reviews might miss, such as changes in sorting stability affecting pricing logic.