VerifyPatch

Verify the patch.

Know what evidence actually supports the change.
Provenance, generated checks, mutation, behavior, and policy. No trust score.

Fully open source.

VerifyPatch

COMPLETE

Patch

Changed executable lines

42

  • PR-untouched18
  • PR-touched only17
  • Unknown2
  • Uncovered5

Test evidence

+ 128 passed

! 2 tests changed

! ASSERT_TO_TRUTHY

Mutation

9 selected

7 killed by PR-untouched

2 killed by PR-touched

Generated checks

4 requirements · 4 passed

Policy

REVIEW

How it works

PATCH #482pricing.py

See where the evidence came from.

pricing.py

- return max(total - 10, 0)

+ return total - 10

test_boundary

test_discount

unknown context

calculate_discount

CI PASS

42

Changed executable lines

  • PR-untouched18
  • PR-touched only17
  • Unknown2
  • Uncovered5

Same green CI. Different evidence.

Illustrative example

Your PR can change the code
and the evidence approving it.

Code

calculate_discount()

- return max(total - 10, 0)+ return total - 10

Tests

test_discount()

- assert discount(5) == 0+ assert discount(15) == 5
CIrunning

Where did the evidence come from?

PR-untouched

Existing evidence

43%

PR-touched

Changed evidence

40%

Green is a result. Provenance is context.

PATCH #482pricing.py

Proof

Tested on real code, not just fixtures.

pypricing.pypytest_pricing.py

src › pricing.py

1def calculate_discount(total):
2 return max(total - 10, 0)
3 return total - 10

$ verifypatch check --base origin/main --head HEAD

✓ complete

8 changed lines

8 PR-untouched

completed in 0.58s

Performance

  • iniconfig+0.35s
  • pluggy+0.54s
  • idna+5.74s
VerifyPatch
preferedevgithub.com/preferedev
Public
Star
  • src/
  • tests/
  • schemas/
  • benchmarks.md
  • USER_MANUAL.md
  • README.md
$ git clone https://github.com/preferedev/VerifyPatch

Clone it. Run it. Inspect it.

See what actually verifies your next patch.

View on GitHubRead the docs