CodeVetter · Repo Unpack · Testing signals
motiondivision/motion
Tests and CI were inspected, not executed; no passing result, coverage percentage, or runtime performance result is asserted. The repository combines co-located Jest tests, React browser tests in Cypress, and Playwright browser suites. Inspected tests exercise registry precedence, presence initialization, playback controls, scroll parity, and React view transitions. Inspection was bounded, and browser support checks, project selection, and CI wiring limit what test existence establishes.
- Jest uses ts-jest and co-located __tests__ patterns; framer-motion separates JSDOM client tests from Node SSR tests, with JUnit output configured for both.
- Effect-registry unit tests assert registration lookup, newest-effect precedence, removal, deduplication, and animation from a readable initial value.
- AnimatePresence tests use React rendering helpers and frame callbacks to check default initial animation, initial={false} suppression, and ordinary rerenders.
- Cypress has separate React 18/19 base URLs and JUnit files; the inspected scroll-accelerate spec checks direct acceleration propagation, non-compositor propagation, and exclusion of chained useTransform.
- Playwright defines Chromium and WebKit HTML projects plus a Chromium React 19 project; CI forbids focused tests, retries twice, uses one worker, and captures traces on first retry. This configuration contains no Firefox project.
- Inspected Playwright tests cover playback/repeat/interruption, compare native and JS scroll progress within 0.01 across positions and resizes, and inspect React view-transition pseudo-animation timing; the latter skips when startViewTransition is unsupported.
- CircleCI builds after an immutable install, then runs Jest, size budgets, React 18, React 19, HTML, and Next.js jobs; its inspected workflow does not schedule the Makefile's test-e2e target that additionally runs Playwright.
- Validation limits are explicit: documentation warns JSDOM lacks WAAPI and real layout, browser tests can skip unsupported APIs, and the inspected CI job list establishes configured execution paths rather than actual run outcomes.