Skip to content

test(e2e): extend visual-regression, performance, mobile, and user-journeys suites - #1433

Open
scriptnovaa wants to merge 1 commit into
solutions-plug:mainfrom
scriptnovaa:test/recreate-e2e-suites-1420-1423
Open

test(e2e): extend visual-regression, performance, mobile, and user-journeys suites#1433
scriptnovaa wants to merge 1 commit into
solutions-plug:mainfrom
scriptnovaa:test/recreate-e2e-suites-1420-1423

Conversation

@scriptnovaa

Copy link
Copy Markdown

Closes #1420
Closes #1421
Closes #1422
Closes #1423

Summary

Extends the four e2e suites recreated for the frontend rebuild to cover what's live today, and sets up the seams for what isn't yet:

  • visual-regression.spec.ts ([Testing] Recreate visual-regression test suite #1420): wait for document.fonts.ready before every full-page screenshot (fixes the font-loading timing flakiness called out in the issue); add Statistics-section baselines (loaded + loading state) — the one real data-fetching page live today, and the natural spot to add markets list/detail baselines once those routes ship.
  • performance.spec.ts ([Testing] Recreate performance e2e suite #1421): add env-configurable LCP/TTI budget assertions for the statistics data page, seeded with a realistic non-trivial dataset instead of an empty one.
  • mobile.spec.ts ([Testing] Recreate mobile e2e suite #1422): fix the touch-target check to the WCAG 2.5.5 44x44px minimum at mobile viewport (previously only checked height >= 40); add a feature-detected mobile nav toggle test; add a mobile browse → connect wallet → bet journey.
  • user-journeys.spec.ts ([Testing] Recreate user-journeys e2e suite #1423): add a full cross-epic journey (browse → connect wallet → bet → view statistics → subscribe to newsletter) asserting that the bet placed is reflected in both the statistics numbers and the user's bet history, not just that each step passes alone.

Note on scope

Markets list/detail pages and wallet-connect/betting UI (#56#58, #68, #76) haven't landed in this repo yet — only the landing page and the Statistics section exist. Those legs are exercised at the API-mock level, following the same pattern already used by the existing "Betting Flow" and market-creation.spec.ts suites. The new describe blocks are where real-UI coverage gets added once those routes ship.

Testing

Not run in this environment (no node_modules/browsers installed); per request, test execution was skipped.

🤖 Generated with Claude Code

…ys suites

Closes solutions-plug#1420, solutions-plug#1421, solutions-plug#1422, solutions-plug#1423

- visual-regression.spec.ts: wait for document.fonts.ready before every
  full-page screenshot to absorb font-loading timing flakiness across
  local/CI/Docker; add Statistics section baselines (loaded + loading state)
  as the one real data-fetching page live today.
- performance.spec.ts: add LCP/TTI budget assertions (env-configurable) for
  the statistics data page, seeded with a realistic non-trivial dataset.
- mobile.spec.ts: fix touch-target assertions to the WCAG 2.5.5 44x44px
  minimum (was checking height >= 40 only) at mobile viewport; add a
  feature-detected mobile nav toggle test; add a mobile browse -> connect
  wallet -> bet journey (wallet/bet legs mocked at the API level, browse
  through the real UI).
- user-journeys.spec.ts: add a full cross-epic journey (browse -> connect
  wallet -> bet -> view statistics -> subscribe newsletter) that asserts
  state from the bet step is reflected in both the statistics section and
  the user's bet history, not just that each step passes in isolation.

Markets list/detail pages and wallet-connect/betting UI (solutions-plug#56-solutions-plug#58, solutions-plug#68, solutions-plug#76)
haven't shipped yet, so those legs are covered at the API-mock level
following the existing pattern in this suite (Betting Flow, market-creation
spec); the new describe blocks are where real-UI coverage gets added once
those routes exist.
@drips-wave

drips-wave Bot commented Aug 27, 2026

Copy link
Copy Markdown

@scriptnovaa Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant