Repository navigation
Add a browser smoke test that fails on console errors and SSR fallbacks for every route #861
Description
None of the runtime failures below were caught by CI, because unit tests mock the environment and the Playwright suite isn't run (see the e2e-in-CI issue):
- 500 on every route without
VITE_NETWORK ReferenceError: ENV is not definedon/trade(Trade confirmation dialog references undefinedENV;mainfailsbun typecheck#825)sessionStorage is not definedduring SSR on/trade,/pools,/faucet- hydration failure on
/gallery - font 404s, duplicate React keys, and the leaked merge-conflict text in the header
Proposal
One Playwright spec (e2e/route-health.spec.ts) that, for each route in src/routes and at desktop and mobile viewports:
- starts from a clean env (only the committed
.env.testnetdefaults) - asserts the HTTP status is 200 (404 for an unknown route)
- fails on any
pageerror, any consoleerror(allow-list external-network failures viapage.routestubs, following the existing helpers ine2e/helpers/), and any "Switched to client rendering" / "Hydration failed" message - fails on same-origin 4xx/5xx responses
- runs axe and fails on critical violations
Acceptance criteria
- Spec added, and it fails against current
main - Runs in CI (with the e2e-in-CI issue)
Found while running the web app locally (bun dev, headless Chromium and axe-core sweep of every route at desktop and iPhone-13 sizes) on 2026-10-15, main @ 4c5cf1d. Contributors: follow AGENTS.md / CONTRIBUTING.md. The full commit gate must pass, with no eslint-disable, .skip, or lowered thresholds.
Activity
guptakumarranjeet150 commentedon Oct 15, 2026
Hi team,
I analyzed "Add a browser smoke test that fails on console errors and SSR fallbacks for every route" in SO4-Markets/interface and have a concrete technical roadmap to resolve it.
Technical Implementation Outline:
no-consoleor strict logger rule) across the workspace.npm run lint/ linter check and unit tests pass with zero warnings.Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!
Ay-obami commentedon Oct 18, 2026
@Ay-obami has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ay-obami to this issue.
Ghoost-404 commentedon Oct 18, 2026
@Ghoost-404 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ghoost-404 to this issue.
Jaydbrown commentedon Oct 18, 2026
@Jaydbrown has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jaydbrown to this issue.
drips-wave commentedon Oct 18, 2026
Congratulations, @Jaydbrown! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Jaydbrown: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
Jaydbrown commentedon Oct 18, 2026
Resolved in #996:
e2e/route-health.spec.tstesting all routes (/,/trade,/pools,/earn,/referrals,/faucet,/gallery,/changelog,/design-system) at both desktop (1440x900) and mobile (390x844) viewports.binance,stellar.org,gmxinfra.io,pyth.network).pageerrors, console errors, SSR hydration mismatches, and same-origin 4xx/5xx responses.drips-wave commentedon Oct 19, 2026
This issue has been completed by @Jaydbrown as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Jaydbrown: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.