Skip to main content
Read the title, know the outcome. The check title says how many changed functions were verified. Open the check for one result per function. It’s advisory: success only when every changed function is Proven same, otherwise neutral, never failure.

​
Every check title, decoded

Every changed function was Proven same. The check is success. Nothing to do, but a proof means “same as before”, not “correct”.
At least one changed function returns a different result for some input. Open the check, find the input, and decide if the change was intended.
An input looks like it differs, but replaying it didn’t confirm it. Run both versions on it before acting. It may be a false alarm.
No differences, but at least one function is No change found, not Proven same. Good evidence. Add tests that cover more inputs.
Some functions weren’t verified. Review them by hand or with tests. See not verified reasons.
A function hit an error. Use Re-run check in the Console. If it keeps failing, contact support.
The run verified none of the changed functions. This isn’t a pass. Check the function list for reasons.
No supported files changed, or only test files did. See when it doesn’t run.

​
Act on each result

You may also see No changed functions to compare (functions were only added, deleted or renamed) or Skipped (the check didn’t run).

​
Not verified reasons

Context functions are unchanged functions checked alongside the change. They never count toward X/Y, but a behavior change in one still keeps the check neutral.

​
Next steps

Formal verification

How the check works.

What is formal verification?

The idea from scratch.