This repository was archived by the owner on Jun 24, 2026. It is now read-only.
Repository navigation
Conversation
Changes:No line counts changed Total lines: 4738 (0) |
deployed preview: https://629.connect-d5y.pages.devWelcome to connect! Make sure to:
Mobile
Desktop
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #292
I added a small browser stress test for Connect and hooked it into
./test.sh.The test uses public demo mode and runs through the main demo flow in Chromium. It checks the dashboard, demo device page, and demo route page on both desktop and mobile.
I kept it intentionally small so it can run as part of the normal test script without turning into a large fuzzing setup. It checks for the main things mentioned in the issue: page crashes, uncaught errors, serious console errors, blank/stuck pages, failed non-media requests, 500+ responses, and long-pending non-media requests.
It does not use real comma credentials or real device data. It also avoids actions that could change account or route state, like unpairing, billing/subscription actions, checkout, route privacy changes, or account mutation.
I tested this in Codespaces.
Passed:
bun run stressbun biome cibun tscbun linesbun bundle-sizeFull
bun run test run/./test.shis currently blocked by an unrelated Mapbox geocoding expectation insrc/map/geocode.spec.ts. I checked cleanupstream/masterat342d3db, and it fails the same way there. PR #622 looks like it already fixes that drift, so I left it out of this PR to keep this focused.