Skip to content

test(app): pin the extraction-grid ordinal convention across the browser/server boundary - #912

Merged
JArmandoAnaya merged 1 commit into
mainfrom
test/848-grid-ordinal-boundary
Oct 12, 2026
Merged

JArmandoAnaya merged 1 commit into
mainfrom
test/848-grid-ordinal-boundary

Conversation

@JArmandoAnaya

Copy link
Copy Markdown
Contributor

Closes #848

Adds a cycle test that imports a mid-clip range (0.25–0.5 s at 8 fps) end to end: the real built materializer decodes vp8.webm in the page, the frames are uploaded to the real server, and the test asserts the first ordinal is nonzero and equals ceil(start x fps) (ordinals [2, 3]), that the stored frame_index and frame_timestamp match, and that the source records the range.

The test drives the materializer and API directly rather than the range timeline, which only selects whole seconds, while every fixture is 1 s long. No fixture or product change.

Verified by mutation: switching either the browser worker or VideoProvenance.selects to selection-relative ordinals fails the test.

Checks run: pnpm --filter @visionset/app cycle video-import (5 passed), pnpm --filter @visionset/app lint.

@JArmandoAnaya
JArmandoAnaya merged commit 819484e into main Oct 12, 2026
31 checks passed
@JArmandoAnaya
JArmandoAnaya deleted the test/848-grid-ordinal-boundary branch October 12, 2026 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The extraction-grid ordinal convention is not pinned across the browser/server boundary

1 participant