Skip to content

fix(tests): wait for loaded content in live layout checks - #332

Merged
ael-dev3 merged 1 commit into
mainfrom
fix/live-content-readiness
Oct 25, 2026
Merged

ael-dev3 merged 1 commit into
mainfrom
fix/live-content-readiness

Conversation

@ael-dev3

Copy link
Copy Markdown
Owner

Behavior

Live layout and interaction checks could accept loading placeholders or inert first-painted cards as ready content. In the phone profile check, the selected card had no measurable box when header geometry was compared. Require a real cast after the wallet data is present, assert that all three boxes exist, and preserve the original geometry comparisons.

Apply the same readiness rule to nine existing live cases: Home interactions wait for app handover, and CSP/phone overflow checks require loaded app cards or posts. First-paint timing, the 100 ms navigation limit, Back geometry/stability, network hooks, test identities and inline request checks are unchanged. There are no runtime, workflow, quota or database changes.

Validation

  • Required scripts/check.sh: 612 native tests, formatting, native/Wasm Clippy and licenses pass.
  • All nine affected live cases pass with one worker and zero retries against the identical deployed product.
  • Three controlled API-gated probes demonstrate the old selectors accepting placeholders; the repaired waits block until data arrives and then retain the original layout, overflow and CSP assertions. This demonstrates the readiness defect without claiming to reconstruct the untraced production null scheduling.
  • The prior full production result remains recorded as failed. Normal CI and a fresh full production pass on the merged revision remain required.

@ael-dev3
ael-dev3 merged commit e992b29 into main Oct 25, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant