zh-CN-translation
4 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Den
|
5822e471c6 |
fix(e2e): stop asserting on SSE reply in activation-positive — closes #90 (#102)
* fix(e2e): stop asserting on SSE reply in activation-positive — CI-harness limitation, not a product bug (closes #90) Extensive investigation (see PR #102 for the full trail) into "the positive flow's assistant reply never renders" tried four independent SSE client transports in src/lib/sdk.ts global.events(): the already-shipped expo/fetch ReadableStream reader, a hand-rolled XMLHttpRequest reader, react-native-sse, and react-native-fetch-api's `reactNative: { textStreaming: true }`. Every one delivers exactly one chunk right after connecting to the mock server and then nothing until the connection closes, regardless of API choice or frame size (a ~4KB padding experiment ruled out a buffer-size threshold). A raw-socket probe (a plain BSD-sockets client with zero React Native involvement, run via `adb shell` through the identical adb-reverse tunnel the app uses) streamed every heartbeat from the mock server incrementally in real time over the same connection. That rules out adb-reverse and the mock's flush behavior and isolates the stall to React Native Android's OkHttp-backed networking layer buffering a long-lived streaming HTTP response in this specific Android-emulator + Node-mock + adb-reverse combination — not a defect in any particular client library. There's no evidence this reproduces against a real opencode server on a real device/network: issue #76's 65 affected users prove real SSE connections stream live agent output in production (the bug they hit was the 401-retry storm, not a missing reply). Since expo/fetch is the already-shipped, production-proven transport and none of the alternatives showed any advantage in this harness, the transport stays unchanged. What changes instead: .maestro/flows/activation-positive.yaml no longer waits on the SSE-streamed reply, since asserting on it here would assert on a CI-harness limitation, not real app behavior. It now verifies everything reliably observable — consent, connect, session creation, and the optimistic local echo of the sent message — and activation-e2e.yml's `continue-on-error: true` (added because this suite had never passed) comes off, so it blocks PRs on regressions in what it does cover. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(e2e): repair stale "401" assertion in activation-negative-401 (refs #90) Removing activation-e2e.yml's continue-on-error surfaced a second, unrelated stale assertion once the suite was actually enforcing again: the negative flow's connect-time-401 case asserts a literal "401" that PR #79 (401/403 auth-stop handling) and #103 (i18n) apparently moved out of what's rendered — "Connection Failed" still passes, "401" now fails. The alert body interpolates two pieces: probeConnection()'s summary (which turns out to be misclassified as "connection actually works now" for this case — diagnostics-classify.ts's `health.ok` only reflects "fetch() didn't throw", not HTTP status, a separate real bug, out of scope for this PR) and testConnection()'s caught error message, which is sdk.ts's apiErrorFor(401, ...) text and always contains the mock's `{"error":"Unauthorized",...}` body per src/lib/api-error.test.ts. Swapped the assertion to "Unauthorized" and added a temporary console.log of both pieces in app/connection/add.tsx to confirm exactly what renders from CI logcat (removed once confirmed). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(e2e): assert alert action buttons, not body text — native AlertDialog body isn't in Maestro's a11y tree (refs #90) The diagnostic added last commit confirmed the Connection Failed alert's body DOES contain the real error ("API Error: 401 - {\"error\":\"Unauthorized\",...}", via logcat: '[connect] failure alert content' logged both the (separately buggy, out-of-scope) probeConnection summary and the correct testConnection error text). Yet both "401" and "Unauthorized" assertions still failed against the same on-screen alert. That means Maestro's accessibility-tree text matching on this Android AlertDialog only sees the title, not the message body — so no substring of the body was ever going to match. Switched to asserting what's actually reachable: the title "Connection Failed" (unchanged, already passing) plus both action button labels, "OK" and "Share report" (src/lib/i18n/en.json common.ok / common.shareReport). That still proves the test's real intent — a visible, actionable error with a dismiss and a share-report path, never a silent failure (issue #76) — using strings actually present in the accessibility tree instead of guessing at unreachable body text. Removes the temporary console.log diagnostic from app/connection/add.tsx now that its purpose (confirming exactly what renders) is done. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(e2e): split activation-e2e into blocking core + non-blocking newer flows (refs #90, refs #104) With this PR's fixes, activation-positive and activation-negative-401 (the coverage issue #90 actually scoped) now run green — but removing activation-e2e.yml's continue-on-error surfaced that four flows added after the initial suite (#82's directory-picker/all-sessions/ variant-picker, #101's diff-scroll) have never once run to completion in CI: they always sat behind whichever activation flow failed first, so they were merged and have run unverified against the current UI/mock this whole time. directory-picker fails immediately at `id: directory-row-frontend`; the other three are untriaged. Fixing four separate, previously-never-green UI surfaces is out of #90's scope and unbounded in this PR. scripts/run-e2e-flows.sh now splits the flow list into CORE_FLOWS (the two #90 covers — blocking, fails the job on a regression) and NEWER_FLOWS (the four newer ones — always run, each one's pass/fail reported via echo/::warning::, but never fails the job). This lets activation-e2e.yml enforce the activation coverage that's now verified, without either leaving it red forever or spending unbounded time inside this PR chasing four unrelated UI surfaces. Filed #104 to track hardening each NEWER flow and moving it back into CORE_FLOWS once confirmed green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> |
||
|
Den
|
6a9bb6d2d5 |
fix(ci): make activation-e2e harness actually run its flows (#91)
Port the harness fixes from test/e2e-new-features to main so the Activation E2E workflow stops failing before any flow executes: - Run everything through scripts/run-e2e-flows.sh as a single script invocation: android-emulator-runner executes each 'script:' line in its own shell, so the previous 'cd artifacts/screenshots' never persisted and maestro failed with 'Flow path does not exist' on every run (19/19 red since the workflow landed). - adb reverse + 127.0.0.1 instead of 10.0.2.2 (unreliable headless), emulator->mock reachability probe, logcat + maestro debug capture. - Trim the flow list to the two flows that exist on main; the three newer flows land with the test/e2e-new-features PR. - continue-on-error until the suite's first green: the positive flow still fails its final reply assertion (mode B in #90), and a never-green suite should not block unrelated PRs or pollute the product-intelligence failure metrics (#89). Refs #90. Refs #89. Co-authored-by: Claude Fable 5 <noreply@anthropic.com> |
||
|
engineer
|
7ca5d2eb19 |
test(activation): address code-review findings on E2E flows, mock, CI
Review fixes (REQUEST_CHANGES round 1): 1. HIGH activation-negative-401.yaml: after dismissing the "Connection Failed" alert the app stays on the Add-Connection modal (handleQuickConnect's failure branch never calls router.back()), so the old `text: "No Connection"` assertion (Sessions-tab empty state) could never pass. Now asserts connect-submit-button is still visible instead. 2. MEDIUM mock-opencode-server.ts: prompt_async now parses the request body, persists the USER's message, and broadcasts it (message.updated + message.part.updated) BEFORE the canned assistant reply — matching real server behavior. Without this, the app's handleEvent strips the optimistic temp- user message when the assistant's message.updated arrives and the sent message vanishes from the transcript. activation-positive.yaml now also asserts chat-bubble-user and the user's message text are visible after the reply lands, so that regression class is actually covered. 3. MEDIUM activation-e2e.yml: timeout-minutes 15 -> 60. The job runs the same npm install + prebuild + assembleRelease + emulator pipeline that cua-smoke.yml budgets 60 min for (emulator-boot-timeout alone is 10 min). 4. MEDIUM activation-e2e.yml: replicated cua-smoke.yml's "Purge stale generated sources" step — the Gradle cache key/restore-keys are shared with that workflow, so the stale-autolinking-tree failure mode (compileReleaseJavaWithJavac against the old package id) applies here too. Verified locally: tsc --noEmit clean; npm test 81/81 pass; all three touched YAML files parse valid; mock server exercised standalone — full prompt cycle confirms GET /session/:id/message returns BOTH user and assistant messages, SSE order is message.updated(user) -> message.part.updated(user) -> busy -> message.updated(assistant) -> message.part.updated(assistant) -> idle, user events carry the sessionID/messageID fields handleEvent filters on, and --fail-auth mode returns 401. Still no emulator run in this environment. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NJKAQ6HAikWGQK7PGZ5Y4E |
||
|
engineer
|
01dd0191b3 |
test(activation): add Maestro E2E coverage for the activation flow
Adds deterministic end-to-end coverage for first-open -> telemetry consent -> server URL entry -> connect -> send first message -> receive reply, targeting the 0%-7-day-retention investigation (GitHub issue #76). - tests/fixtures/mock-opencode-server.ts: dependency-free HTTP+SSE stub matching the REAL client protocol (src/lib/sdk.ts) — REST + a single long-lived GET /global/event SSE stream, no WebSocket. Supports a --fail-auth mode that 401s every request to exercise the connect-time auth-failure class. - .maestro/flows/activation-positive.yaml: consent -> quick connect -> new session -> send message -> assert streamed reply renders, with a screenshot at every step (positive-S1..S8). - .maestro/flows/activation-negative-401.yaml: same setup against the --fail-auth server, asserts Quick Connect's existing "Connection Failed" alert is shown (not silently swallowed) and that the connection is not saved. Flags in comments that Advanced-mode Save (handleAdvancedSave) still has no testConnection() check and is a known, uncovered gap. - testID props added (no restructuring) to the screens/components the flows drive: TelemetryConsentModal, connection/add.tsx, tabs/index.tsx, session/[id].tsx, MessageBubble. - .github/workflows/activation-e2e.yml: new CI job — Android emulator via reactivecircus/android-emulator-runner, builds the debug-signed APK, starts both mock server instances, runs both Maestro flows, uploads screenshots via actions/upload-artifact. Kept separate from the existing vision-driven cua-smoke.yml, which needs a live server + LLM and isn't suited to tight deterministic regression assertions. - .gitignore: Maestro takeScreenshot output is never committed. Verified locally: mock server exercised standalone via curl (health, project/current, path, session create, SSE event ordering, message persistence) in both normal and --fail-auth modes; both Maestro flow files validated as well-formed YAML; tsc --noEmit clean on all changed files. No lint script exists in this repo (N/A). Full emulator execution was not run — no Android SDK/emulator available in this environment. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NJKAQ6HAikWGQK7PGZ5Y4E |