You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ddba75f
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/evidence/android-automation-performance-2026-10-19.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,3 +63,5 @@ Full-suite investigation exposed a pre-existing Android live-text bug on both ba
63
63
An early native-fill implementation omitted the keyboard-opening tap; the lifecycle scenario detected it and the focus tap was restored. One checkout submission miss occurred before the final synchronization and freshness hardening; six isolated checkout replays passed, so its cause was not established. The final combined suite passed, including every replay without retries.
64
64
65
65
Input-socket and screenshot-default regressions failed on unchanged production code (`3 failed, 17 passed`) and passed with the implementation. The focus-path regression also failed on unchanged base. The text-identity regression was observed red and green at its owning hierarchy seam, and its contract and daemon forwarding tests passed.
66
+
67
+
The broad unit selection initially exposed stale screenshot expectations, an inconsistent foreground fixture, and added eager imports. Their fixes passed 1,016 focused tests. The Android TV provider timeout also reproduced on unchanged base: its accepted IME installation was followed by an empty registration list. The fixture now reports the installed service; both Android provider scenario files passed seven tests without a timeout increase.
0 commit comments