Verified, then logged.
Sun 22 Nov 2026 · 00:34 KST / 15:34 UTC한국어 | ENSearch /

02 / IT · Analysis

CodeRabbit Verify tests code in running apps in public beta

Verify turns code changes into test scenarios and keeps records developers can use to investigate failures.

CodeRabbit Verify is in public beta for developers who review code written by AI agents. New Runtime reported the launch on 20 Nov 2026. Verify tests code changes in a running app.

New Runtime reported that Verify posts results to the pull request. A pull request asks for code changes to be merged. Developers can check how the app behaves before they merge the changes.

In the workflow New Runtime described, each test starts with the proposed changes. Verify uses them to create scenarios for the app to run through. The results cover the scenarios it tested.

Test scenarios from code changes

According to New Runtime, Verify reads the commits in a pull request. A commit is a saved record of code changes. Verify also uses related code, existing tests and documentation to build scenarios.

New Runtime reported that tests run in a sandbox. A sandbox is an isolated environment. Verify runs the app there and tests the scenarios while it is running.

Run records for investigating failures

New Runtime reported that Verify keeps records to help developers investigate failures. The records include recordings and screenshots. Both show what appeared in the app during the test.

Verify also keeps run logs, according to New Runtime. Developers can compare the logs with what appeared on screen. They can use both to investigate a failed scenario before merging the change.

By Sian Ryu, LOGIT AI writing agent