test(studio): add timeline performance fixtures#2632
Draft
miguel-heygen wants to merge 1 commit into
Draft
Conversation
This was referenced Jul 19, 2026
Collaborator
Author
This was referenced Jul 19, 2026
This was referenced Jul 19, 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
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.
What
add timeline performance fixtures.
Why
Make Studio timeline performance measurable and enforceable before changing rendering behavior.
How
Adds the focused performance budget, fixture, or browser contract represented by this stack layer.
Key files in this layer:
packages/studio/src/hooks/useStudioTestHooks.test.tsxpackages/studio/src/hooks/useStudioTestHooks.tspackages/studio/src/player/lib/timelinePerformanceFixture.tsTest plan
Validated on the complete stacked tip with formatting, lint, Studio typecheck, the full production build, and the Studio test suite (2,946 passing; 18 todo). Focused timeline/thumbnail tests and browser QA cover the affected interaction path.
Post-Deploy Monitoring & Validation