@sun-asterisk/sungen 3.2.30 → 3.2.32

package/src/orchestrator/templates/appium-environment/setup.sh

@@ -0,0 +1,88 @@
+#!/usr/bin/env bash
+# setup.sh — macOS entry point of the sungen Appium environment bundle.
+#
+#   ./appium-environment/setup.sh [--check] [--skip-android] [--skip-ios] [--no-profile]
+#
+# Emitted by `sungen init --mobile` / `sungen capability add mobile`, which also run it once.
+# Re-run it any time: every step is check → install → verify and a satisfied step is skipped.
+#   --check          report what is missing, install nothing (side-effect free)
+#   --skip-android   skip JDK / Android SDK / uiautomator2
+#   --skip-ios       skip Xcode CLT / applesimutils / xcuitest
+#   --no-profile     do not write the ANDROID_HOME / JAVA_HOME / PATH block to your shell profile
+# Exit: 0 ready (or only warnings) · 1 something failed · 2 unsupported OS / bad flag
+set -u
+
+BUNDLE_DIR=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
+PROJECT_DIR=$(cd "$BUNDLE_DIR/.." && pwd)
+export PROJECT_DIR
+. "$BUNDLE_DIR/scripts/common/lib.sh"
+
+usage() { sed -n '4,13p' "${BASH_SOURCE[0]}" | sed 's/^# \{0,1\}//'; }
+
+for arg in "$@"; do
+  case "$arg" in
+    --check)        SUNGEN_ENV_CHECK_ONLY=1 ;;
+    --skip-android) SUNGEN_ENV_SKIP_ANDROID=1 ;;
+    --skip-ios)     SUNGEN_ENV_SKIP_IOS=1 ;;
+    --no-profile)   SUNGEN_ENV_NO_PROFILE=1 ;;
+    -h|--help)      usage; exit 0 ;;
+    *) printf 'unknown flag: %s\n\n' "$arg" >&2; usage >&2; exit 2 ;;
+  esac
+done
+
+case "$(uname -s)" in
+  Darwin) ;;
+  Linux)
+    printf 'ℹ Linux detected — this bundle provisions macOS and Windows.\n'
+    printf '  Android on Linux: see README.md → "Manual fallback" (JDK + Android SDK via your package manager,\n'
+    printf '  then `sungen capability add mobile` for the project-local Appium + uiautomator2).\n'
+    exit 0 ;;
+  *) printf '✗ unsupported OS: %s (macOS: setup.sh · Windows: setup.ps1)\n' "$(uname -s)" >&2; exit 2 ;;
+esac
+
+cd "$PROJECT_DIR"
+if [ "$SUNGEN_ENV_CHECK_ONLY" = 1 ]; then section "sungen · Appium environment — check only (macOS)"
+else section "sungen · Appium environment setup (macOS)"; fi
+printf '%sproject: %s%s\n' "$C_DIM" "$PROJECT_DIR" "$C_RESET"
+
+# ── 1/5 prerequisites ──────────────────────────────────────────────────────────────────────────
+section "1/5  Prerequisites"
+. "$BUNDLE_DIR/scripts/common/verify-node.sh"
+
+brew_check()   { have brew && printf 'brew at %s' "$(command -v brew)"; }
+brew_install() {
+  NONINTERACTIVE=1 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" || return 1
+  # The installer does not touch the running shell — pick brew up for the rest of this run.
+  if [ -x /opt/homebrew/bin/brew ]; then eval "$(/opt/homebrew/bin/brew shellenv)"
+  elif [ -x /usr/local/bin/brew ]; then eval "$(/usr/local/bin/brew shellenv)"; fi
+}
+brew_verify()  { brew_check || { printf 'Homebrew not found after install — https://brew.sh, then re-run'; return 1; }; }
+run_step "Homebrew" brew_check brew_install brew_verify
+
+# ── 2/5 Android ────────────────────────────────────────────────────────────────────────────────
+if [ "$SUNGEN_ENV_SKIP_ANDROID" != 1 ]; then
+  section "2/5  Android (JDK, SDK, adb, emulator)"
+  . "$BUNDLE_DIR/scripts/macos/install-android.sh"
+else
+  section "2/5  Android"; log_skip "Android toolchain" "--skip-android"
+fi
+
+# ── 3/5 iOS ────────────────────────────────────────────────────────────────────────────────────
+if [ "$SUNGEN_ENV_SKIP_IOS" != 1 ]; then
+  section "3/5  iOS (Xcode, applesimutils)"
+  . "$BUNDLE_DIR/scripts/macos/install-ios.sh"
+else
+  section "3/5  iOS"; log_skip "iOS toolchain" "--skip-ios"
+fi
+
+# ── 4/5 Appium ─────────────────────────────────────────────────────────────────────────────────
+section "4/5  Appium (project-local) + platform drivers"
+. "$BUNDLE_DIR/scripts/common/install-appium.sh"
+
+# ── 5/5 health ─────────────────────────────────────────────────────────────────────────────────
+section "5/5  Health check"
+[ "$SUNGEN_ENV_SKIP_ANDROID" != 1 ] && . "$BUNDLE_DIR/scripts/macos/verify-android.sh"
+[ "$SUNGEN_ENV_SKIP_IOS" != 1 ]     && . "$BUNDLE_DIR/scripts/macos/verify-ios.sh"
+. "$BUNDLE_DIR/scripts/common/verify-appium.sh"
+
+print_summary

package/src/orchestrator/templates/specs-checked-state.ts

@@ -38,7 +38,7 @@ const POLL_INTERVAL_MS = 100;
 export interface DeclaredSignal { class?: string; attribute?: string }
 
 /** Where the control publishes its on/off state — decided in the page, from the real element. */
-export type StateSource = 'native' | 'aria-pressed' | 'aria-checked' | 'class' | 'attribute' | 'none';
+export type StateSource = 'native' | 'aria-pressed' | 'aria-checked' | 'aria-selected' | 'aria-current' | 'class' | 'attribute' | 'none';
 export interface ControlProbe {
   source: StateSource;
   /** Current state, already normalised. Meaningless when `source` is 'native' (Playwright reads it). */
@@ -110,6 +110,24 @@ export function probeControl(node: unknown, declared?: DeclaredSignal): ControlP
   }
   // Role claims checkable but nothing is published — let Playwright raise its own, precise error.
   if (ariaCheckableRole) return { source: 'native', on: false, buttonLike };
+  // `is selected` on a tab, an option, a chip or a nav item. These publish `aria-selected` or
+  // `aria-current`, which nothing above reads: the probe fell straight through to 'none' and the
+  // step failed saying the control has no on/off state to set, on a control that publishes one in
+  // the standard place. Read here rather than in the templates so a suite already generated in the
+  // field picks the fix up without regenerating — the same reasoning the URL predicate is a runtime
+  // helper for.
+  //
+  // `aria-current` is not a boolean: the spec allows 'page', 'step', 'location', 'date', 'time' and
+  // 'true', and only the literal 'false' (or the attribute's absence) means off. Read that way
+  // round, so `aria-current="page"` on the active nav item reads as ON rather than as a stray
+  // non-'true' string.
+  if (el.hasAttribute('aria-selected')) {
+    return { source: 'aria-selected', on: String(el.getAttribute('aria-selected') ?? '').trim().toLowerCase() === 'true', buttonLike };
+  }
+  if (el.hasAttribute('aria-current')) {
+    const raw = String(el.getAttribute('aria-current') ?? '').trim().toLowerCase();
+    return { source: 'aria-current', on: raw !== '' && raw !== 'false', buttonLike };
+  }
   return { source: 'none', on: false, buttonLike };
 }
 
@@ -132,11 +150,18 @@ const sleep = (ms: number): Promise<void> => new Promise((r) => setTimeout(r, ms
  */
 const left = (deadline: number): number => Math.max(250, deadline - Date.now());
 
+/** The sources that name an ATTRIBUTE the live state can be re-read from. */
+type AttributeSource = 'aria-pressed' | 'aria-checked' | 'aria-selected' | 'aria-current';
+
 /** Read the live state. A REMOVED attribute means off: `aria-pressed={on || undefined}` is a common
  *  React/Vue idiom, so requiring a literal "false" would fail a control that is correctly off. */
-async function readOn(target: Locator, attr: 'aria-pressed' | 'aria-checked', deadline: number): Promise<boolean> {
-  const raw = await target.getAttribute(attr, { timeout: left(deadline) });
-  return String(raw ?? '').trim().toLowerCase() === 'true';
+async function readOn(target: Locator, attr: AttributeSource, deadline: number): Promise<boolean> {
+  const raw = String(await target.getAttribute(attr, { timeout: left(deadline) }) ?? '').trim().toLowerCase();
+  // `aria-current` is the one non-boolean of the four: the spec allows 'page', 'step', 'location',
+  // 'date', 'time' and 'true', so only the literal 'false' (or absence) means off. Read the other
+  // way round it would report the active nav item as OFF.
+  if (attr === 'aria-current') return raw !== '' && raw !== 'false';
+  return raw === 'true';
 }
 
 /**
@@ -238,12 +263,12 @@ export async function setCheckedState(
     // Not pressable and publishes nothing — there is no reading of this that makes the step meaningful.
     throw new Error(
       `Cannot ${want ? 'check' : 'uncheck'} [${label}] — it is not a checkbox/radio/switch, is not a `
-      + `button, and publishes no aria-pressed/aria-checked, so it has no on/off state to set. Point the `
+      + `button, and publishes no aria-pressed/aria-checked/aria-selected/aria-current, so it has no on/off state to set. Point the `
       + `selector at the control itself, or give it a real ARIA toggle role.`,
     );
   }
 
-  const attr = probe.source;
+  const attr: AttributeSource = probe.source as AttributeSource;
   // Already in the requested state → nothing to do. This is the idempotence `check` promises.
   if (probe.on === want) return;
   await target.click({ timeout });

package/src/orchestrator/templates/specs-mock.ts

@@ -25,7 +25,8 @@ export interface MockConfig {
   name: string;
   method: string;               // HTTP verb or '*'
   url: string;                  // page.route glob, or 're:<pattern>' for a regex
-  status: number;
+  status?: number;              // the server ANSWERED — absent exactly when `abort` is set
+  abort?: string;               // the request NEVER ARRIVED — a route.abort() errorCode
   headers?: Record<string, string>;
   body?: string;                // pre-serialized by the compiler (JSON string)
   delay_ms?: number;
@@ -104,9 +105,16 @@ class MockRouter {
       if (cfg.method !== '*' && route.request().method() !== cfg.method) return route.fallback();
       st.counts.set(cfg.name, (st.counts.get(cfg.name) ?? 0) + 1);
       if (cfg.delay_ms) await new Promise((r) => setTimeout(r, cfg.delay_ms));
-      // A delayed fulfill can race a page close / reset at teardown — that race must
-      // not surface as an unhandled rejection from inside a route handler.
-      try { await route.fulfill({ status: cfg.status, headers: cfg.headers, body: cfg.body }); } catch { /* page closing */ }
+      // A delayed response can race a page close / reset at teardown — that race must
+      // not surface as an unhandled rejection from inside a route handler. It wraps BOTH
+      // outcomes: an abort races teardown exactly like a fulfill does.
+      try {
+        // `abort` is the request that never reaches the server; `status` is the one the
+        // server answered. The catalog refuses an entry carrying both, so this is a real
+        // either/or, not a precedence rule (#676).
+        if (cfg.abort) await route.abort(cfg.abort);
+        else await route.fulfill({ status: cfg.status, headers: cfg.headers, body: cfg.body });
+      } catch { /* page closing */ }
     };
     await page.route(pattern, handler);
     st.routes.push({ pattern, handler });