Repository navigation
updated wiki doc for frontend test workflow - #549
Merged
BenHenning merged 2 commits intoNov 3, 2026
Merged
Conversation
Contributor
Author
|
@HardikGoyal2003 PTAL!! |
Contributor
Author
|
@HardikGoyal2003 Friendly ping!! |
HardikGoyal2003
requested changes
Nov 3, 2026
Contributor
Author
|
@HardikGoyal2003 PTAL!! |
Contributor
Author
|
@seanlip can you merge this PR . Thanks!! |
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
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.
Fixes #548.
Documents the Stress Test (Frontend Unit Tests) workflow in Frontend-tests.md, mirroring the acceptance test "Reproduction" section: when to use it, how to trigger it from a fork, its num_runs/specs_to_run inputs, and how to replay the failing run's Jasmine seed locally. Also cross-links from Debug-frontend-tests.md so readers stop hand-rolling repeated local runs.