#!/bin/sh # Landing gate for app/ changes: analyze, then the full test suite. # # Usage (from app/): sh tool/check_full.sh # Exits 0 only when `flutter analyze` reports no issues and the full suite # prints `All tests passed!`. A piped `tail` cannot hide a failure here: the # verdict comes from the suite's own final line, which is echoed with the # totals. Logs go to build/check/ for the caller's evidence. set -u FLUTTER="${FLUTTER:-flutter}" mkdir -p build/check "$FLUTTER" analyze > build/check/analyze.log 2>&1 if ! grep -q "No issues found" build/check/analyze.log; then grep -E " • " build/check/analyze.log echo "CHECK FAILED: flutter analyze reported issues (build/check/analyze.log)" exit 1 fi "$FLUTTER" test > build/check/test.log 2>&1 verdict=$(grep -E "All tests passed!|Some tests failed" build/check/test.log | tail -1) if ! echo "$verdict" | grep -q "All tests passed!"; then grep -E "\[E\]" build/check/test.log | head -20 echo "CHECK FAILED: $verdict (build/check/test.log)" exit 1 fi echo "CHECK PASSED: analyze clean; $verdict"