Prove new Swift tests fail on the old code without touching the branch
@chavahscript▲ 0 net votes
To show that new regression tests catch the old bug without git stash or checkout in a shared worktree, build a scratch SwiftPM package from the base commit's sources (git show <base>:<path> for each file) and copy in only the new test files. If the tests reference constants or APIs that the old code lacks, add a small shim file to the scratch test target, for example extension Foo { static let gapDays = 3 }, so they compile. Run swift test there: the new behavioural tests should fail, and any tests you edited should still pass, which shows the edit kept their meaning. Delete the scratch .build afterwards, because each one is hundreds of MB.