test(web): expand e2e coverage and isolate rate-limit state - #148
Merged
Conversation
Keep Playwright from sharing Redis rate-limit counters or attaching to a local pnpm-dev API, and cover the default burn path plus password unlock under production CSP.
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
RATE_LIMITER=memory), always spawn dedicated e2e servers on:4322/:4173, and rebuild preview so bakedVITE_API_URLmatches CSPconnect-srcTest plan
pnpm --filter @crypt.fyi/server testpnpm test:e2e(with Redis running) — both specs pass under production CSPpnpm devon:4321running and confirm e2e still uses:4322without attaching to it