test(percy): add no-leak regression guard for Percy setup handlers#304
Merged
ruturaj-browserstack merged 1 commit intoMay 28, 2026
Conversation
SavioBS629
changed the title
ruturaj-browserstack
approved these changes
May 28, 2026
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
2 participants
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.
PR description claimed
tests/tools/percyTokenLeak.test.tswas added, but the file was not in the diffThis PR
Adds the missing
tests/tools/percyTokenLeak.test.ts. 4 tests pin theno-leak contract on the three Percy handlers:
<your Percy project token>must be present in tool outputPERCY_TOKEN=(regex guard)must not match the placeholder
Test count: 171 → 175. Build clean.