OpenTagViewer: Skill for Claude Code

Watching a test run to a verdict

The emulator suite takes upwards of ten minutes, so it gets backgrounded, so something has to report on it. Do not write that something fresh each time. Use the script.

# 1. Start the run, redirected to a file.
./gradlew :app:testEmulatorDebugAndroidTest --console=plain > tmp/run.log 2>&1

# 2. Prove the watcher sees the log before trusting it. One command, always.
python .claude/skills/watch-gradle-tests/watch_tests.py tmp/run.log --once

# 3. Arm a Monitor on the same script with no --once.
python .claude/skills/watch-gradle-tests/watch_tests.py tmp/run.log

Each line it prints is one event: FAILED <Class>.<method> as each failure appears, STALLED … if the log stops growing, and FINISHED + VERDICT at the end.

Give every run its own log file

Reusing one name races the watcher against the run that is starting. Arm a Monitor while the previous run's log is still on disk and it reads that — matches its BUILD line, prints its verdict, and reports a finished run that has not started. The XML age in VERDICT is the only hint, and "2 min old" looks perfectly current.

That cost a wrong conclusion here: a stale verdict was read as the new run's, its crash trace pointed at a line number the fix had already moved, and the obvious inference — "the APK did not rebuild" — was wrong twice over.

log=tmp/run-$(date +%H%M%S).log
./gradlew :app:testEmulatorDebugAndroidTest --console=plain > "$log" 2>&1 &
python .claude/skills/watch-gradle-tests/watch_tests.py "$log"

Never wrap --once in your own sleep loop

That is the shape step 3 exists to replace, and it looks close enough to right to pass review:

# WRONG - and this exact loop cost 1h22m
for i in $(seq 1 110); do
  grep -qE "BUILD SUCCESSFUL|BUILD FAILED" tmp/run.log && { ...--once; break; }
  sleep 20
done

It waits for a terminal line and nothing else, so it is blind to the run stopping without one — which is the failure worth catching. A suite hung 25 minutes on a single test produced no new output and no verdict, so the loop sat silent, then hit its own limit and exited 0 with no output at all: indistinguishable from success. Meanwhile watch mode would have said STALLED no output for 8 min, at 424/687 seventeen minutes earlier.