Choose the check for the changed behavior
Run source Make targets from the repository root, after locked dependency setup, adding DOCKER_CONTEXT=your-local-context. These are explicit application checks. For documentation changes, follow Documentation authoring to build the site and check generated links and navigation.
To edit a form label and preview it locally, follow Change a screen locally.
Source and generated resources
| Target | Evidence or effect |
|---|---|
cam/conformance/check | Manifest/resource integrity, ABI joins, route arguments, UI composition and typeflow. |
cam/abi/export | Writes manifest-declared ABIs and refreshes integrity pins. Inspect the Git diff; a second export should be unchanged. |
cam/integrity/refresh | Refreshes the explicitly admitted manifest/protocol outputs after authored changes. |
tests/checks, js/tests | Repository rules and JavaScript package/tool tests. |
dapps/build, dapps/scripts/build, dapps/tests | Solidity compilation, deterministic/fuzz tests and stateful invariants. |
tests | Full automatic campaigns, including disposable real-RPC scenarios and the networked dependency-egress check. |
For Escrow formatting and release-tool work, use escrow/format, dapps/format/check and escrow/release/check as applicable. Formatting and export targets can change source resources; they are not merely read-only assertions. Dependency installation stays a separate, explicit networked step.
Pay-to-Play: actual settlement and recovery
make pay-to-play/local/recovery/run DOCKER_CONTEXT=your-local-contextThis first runs the payment scenario, then recovery on its owned disposable chain. Payment coverage includes canonical invoice hashes, on-chain v2 digests, substituted-reference rejection, partial collection, later-invoice-first allocation and merchant receipts. Recovery covers renewal, early closure, exact phase cutoffs, refund destinations, permissionless refund, reuse and multi-customer retirement.
The campaign also exercises incoming-move discovery and the file-backed refund worker with bounded batches and journal persistence, including a confirmed transaction followed by a fatal journal-write failure. Neither campaign selects a real operator deployment. Use pay-to-play/local/scenario/run for payment only and pay-to-play/refunds/check for offline worker checks; invoice-helper tests run in js/tests.
Escrow: nine complete settlement paths
make escrow/local/scenario/run DOCKER_CONTEXT=your-local-contextThe deterministic campaign follows authored actions through preparation, simulation, submission, receipt and continuation—not direct business writes alone. It covers client cancellation, normal approval, acceptance/work/review timeouts, both arbitrator awards and both arbitration-timeout beneficiaries. Every path uses a fresh reference, switches the viewing actor, checks the terminal state and withdraws the complete credit.
Solidity fuzzing separately checks action boundaries immediately before, at and after deadlines. Stateful tests cover concurrent agreements, liability conservation, complete settlement, event/storage agreement and terminal irreversibility. See the accounting and projection reference.
Bike: distinct actors before a random walk
make bike-nft/local/integration/fuzz/fixture-writes/run DOCKER_CONTEXT=your-local-contextThe deterministic seller/workshop/buyer sequence proves registration, scoped metadata access, transfer, loss of former authority and a buyer update. Its success marker is bike_actor_ok. The subsequent generic walker is single-account; it does not independently prove distinct-actor behavior. All keys and funds belong to the private disposable fixture.
Inspect Escrow without signing
make escrow/local/demo/terminal/up \
DOCKER_CONTEXT=your-local-context COMPOSE_PROJECT_NAME=cam-terminalThe terminal uses real fixture reads but only prepares writes. Use account <address> to inspect another role or account none for an anonymous view. It does not sign or submit. Let cleanup finish on exit; use escrow/local/demo/terminal/down with the same context/project if resources remain.
Choose the live-browser boundary explicitly
Start the relevant disposable GUI and a dedicated loopback-CDP browser. Supply the entire printed viewer URL and the expected nonzero CAM commitment from the fixture you intend to test:
make escrow/live/browser/check \
DOCKER_CONTEXT=your-local-context COMPOSE_PROJECT_NAME=cam-demo \
CDP_ORIGIN=http://127.0.0.1:9222 \
VIEWER_URL='the full printed GUI URL' \
EXPECTED_CAM_URI='the expected manifest URI' \
EXPECTED_CAM_HASH='the expected 0x-prefixed SHA-256'| Target | What it may change |
|---|---|
escrow/live/browser/check | Owns a test tab; checks reads, navigation, integrity and layout. No wallet-signed writes. |
escrow/live/browser/fixture-writes/check | Owns test tabs and submits local transactions, including dispute/withdrawal and rejection or uncertain-response recovery. |
pay-to-play/live/browser/check | Submits local payment/withdrawal/refund transactions and tests voucher drafts, events, integrity and narrow layout. |
The signing lanes require chain 31337 and matching fixture resources; use only state you can discard. They close their own tabs but leave your existing browser and GUI services running. Their injected providers do not qualify a real wallet extension's confirmation interface or physical-pointer interaction.
Payment browser coverage includes a separate zero-wait recovery channel, not every recovery operation; renewal and retirement also have contract, viewer and real-RPC coverage. A passing local campaign establishes local behavior, not delivered work or a public service's readiness.
Source: supported entrypoints. For another repository's service tests, use the fixture handoff, not the manual browser launcher.