CodeVetter · Repo Unpack · Testing signals
storybookjs/storybook
Tests and CI definitions were inspected, not executed; no passing result or measured coverage is asserted. Vitest combines package projects with a separate browser-backed Storybook UI project. Inspected tests exercise rendering contracts, source mutation, token validation, and CLI attachment. Explicit exclusions and mocked boundaries limit what those tests demonstrate, and the inventory is bounded rather than exhaustive.
- The root Vitest configuration includes agent-eval and package projects, uses threads and Istanbul coverage, and excludes story files from coverage; the Storybook browser project is omitted on Windows CI.
- The core Vitest project enables type checking, Node resolution for oxc modules, a Polka URL alias, and separate benchmark file inclusion.
- storybook-ui uses addon-vitest, includes the vitest tag, runs headless Chromium through Playwright, and loads the internal Storybook setup file.
- Browser story tests explicitly exclude Zoom, docs blocks, benchmarks, and UseState names; SaveStory's Created play asserts a mocked createStory callback, but its meta carries !vitest.
- StoryRender unit tests use mock renderers/stores and assert autoplay true/false behavior; those assertions exercise lifecycle decisions rather than a real browser/framework rendering integration.
- CSF arg-mutation tests load fixture files, parse their ASTs, apply updateArgsInCsfFile, and assert unsupported forms reject; token tests cover missing, empty, unequal-length, special-character, and Unicode inputs.
- tools-attach Playwright tests launch the compiled CLI and check required attach, auto attach, local interception, and silent no-instance fallback; live attachment cases skip against static builds.
- Fork CI defines Linux/Windows unit jobs and installs Chromium, while NX CI has only workflow_dispatch enabled and retains a job condition for PR/push/schedule events; these definitions were inspected without running them.