Documentation
¶
Overview ¶
cmd/test_wall_upgrade is a manual verification tool for the wall-upgrade system. It drives the same RunWallUpgradeLoop function that the main Bot uses, but exposes three progressively deeper verification steps so a developer can confirm that everything from device connectivity through template recognition to the full loop works on their machine.
Modes:
check (default) Verifies prerequisites only — ADB connected,
device resolvable, calibration sane, required
templates loaded. NO clicks. Safe to run on
any game state.
dry-run Verifies prerequisites PLUS captures the current screen
and runs template-matching for each of the
three required templates (text_wall,
btn_upgrade_wall, btn_confirm_upgrade). Saves
an annotated screenshot with the highest-
confidence match overlaid per template. NO
clicks. Best run while the game is parked at
a representative point of each phase (e.g.
open the builder menu before running).
run Verifies prerequisites, dry-run, THEN prompts for
confirmation (skippable with -yes) and invokes
RunWallUpgradeLoop for real. Each phase
boundary emits a screenshot
(output/wall_upgrade_tests/<ts>/<step>.png)
and a JSONL phase log. Use this to confirm
the FULL sequence works end-to-end — start
with the game on MainVillage.
All screenshots + JSONL phases are saved under ./output/wall_upgrade_tests/<timestamp>/ relative to the working dir.
Click to show internal directories.
Click to hide internal directories.