verification-runner

To record evidence for automated testing before a software handoff, execute final proof commands on your checkout. The runner logs the command, exit status, key output, and file changes to verify compliance.

Proof running in software compliance is the execution of final verification commands to generate definitive evidence of a successful pass. It is needed before production handoffs to confirm code meets all standards.

Yes, the verification runner requires Gradle to execute proof commands. You trigger the process by running the Gradle task, which automates the testing and captures the required handoff evidence.

Yes, you can use this script to log command output for SaltMarcher passes. It specifically executes assigned proof commands on the final checkout and records execution details for compliance review.

The best way to automate test evidence logging for production handoffs is using a standardized verification runner. It executes final proof commands and automatically records exit statuses and output for compliance.

When recording execution details for handoff standards, the runner captures the exact proof command used, the exit status, key output logs, and any file changes that occurred after the run completed.