Open Brain
Meta AIEngineering PostOfficial Source

Catching Bugs Before They Land: JiTTesting’s Human-on-the-Loop Approach at Full Scale

Meta generates tests that expose behavioral changes in risky diffs, then combines deterministic rules, an LLM ensemble, and aggregate human review to filter likely false positives before code lands.

Meta AI · Oct 29, 2026
Open Source Open MarkdownOpen JSON
Source Summary

Meta’s JiTTests target risky diffs and generate executable tests through two workflows: one infers change intent and risks; the other probes behavioral differences. A rules engine and LLM ensemble rank failures before engineers review selected results. In H1 2026, the system caught **74 privacy bugs** before production; **60%** of reported findings were true positives.

Practical Implication

For coding agents, consider adding tests that demonstrate a diff’s behavioral change to the review pipeline. Meta’s setup also suggests routing only ranked findings to engineers, with people setting criteria and reviewing outcomes in aggregate.

Agent-Ready Context
Meta’s JiTTests target risky diffs and generate executable tests through two workflows: one infers change intent and risks; the other probes behavioral differences. A rules engine and LLM ensemble rank failures before engineers review selected results. In H1 2026, the system caught **74 privacy bugs** before production; **60%** of reported findings were true positives.

For coding agents, consider adding tests that demonstrate a diff’s behavioral change to the review pipeline. Meta’s setup also suggests routing only ranked findings to engineers, with people setting criteria and reviewing outcomes in aggregate.

The system runs overnight on spare capacity and targets risky changes, so the material does not establish immediate coverage for every diff. The reported results come from Meta’s infrastructure and may depend on its codebase and review process.
Connected Context · Feed7 Judgment

JiTTesting provides a large-scale example of risk-ranked, human-reviewed tests that probe a diff's intended or observed behavior, with reported privacy-bug findings and a stated true-positive rate. It gives concrete support for integrating behavioral evidence into agent code review, while its overnight, risk-targeted setup leaves immediate universal coverage unproven.

Guide, Verify, Solve — Anirban Chatterjee, SonarBoth argue that verification must be part of the coding loop; JiTTesting adds ranked, executable tests aimed at risky diffs, while Sonar emphasizes repeatable checks and warns that throughput can coexist with persistent quality issues.How to Kill the Code Review — Ankit Jain, AviatorJiTTesting supplies executable behavioral evidence for review, complementing the proposal to shift human review from line-by-line diffs toward verification evidence and retained intent.The AI bugpocalypse is here. Now what? - Jack Cable, CorridorJiTTesting operationalizes security review within the development pipeline by generating and ranking tests for risky changes, aligning with the candidate's call to put security review inside coding-agent workflows.We let an AI agent execute Bash and lived to talk about it — Sarah Sanders, PostHogBoth use layered controls for agent-related security; JiTTesting ranks and reviews behavioral findings, while PostHog's candidate emphasizes deterministic policy enforcement and cautions against relying on detection alone.
Context Map
agentcodingsecurity#harness-engineering#agent-reliability
Uncertainty
The system runs overnight on spare capacity and targets risky changes, so the material does not establish immediate coverage for every diff. The reported results come from Meta’s infrastructure and may depend on its codebase and review process.