CodeVetter · Repo Unpack · Testing signals
TanStack/table
Tests and CI were inspected, not executed; no passing result or coverage percentage is asserted. Examined suites span core semantics, React integration, worker protocol bookkeeping, declaration generation, and browser examples. Coverage configuration is report-only, and the inspected browser configuration targets Desktop Chrome. Inspection was selective, so coverage omissions below describe limits of particular checks rather than whole-repository absence.
- table-core uses Vitest with jsdom, globals, fixture setup, and V8 coverage of src/**. Its configuration explicitly enforces no coverage thresholds, so a generated report alone is not a coverage gate.
- Core implementation tests exercise prototype-named column IDs, null-prototype lookup maps, and merged-cell selection expansion, including checks that neighboring cells remain unselected.
- React tests use Testing Library and Vitest for adapter ownership/lifecycle, a regression involving unstable data and controlled expansion, and Node-environment server rendering of state, headers, cells, and footers.
- The inspected worker unit harness replaces Worker with FakeWorker and asserts data-identity messaging, single-flight behavior, trailing stage requests, and rebuilt row order; these assertions do not themselves exercise real worker bundling or structured-clone transport.
- Playwright selects tests through PLAYWRIGHT_TEST_DIR, uses one Desktop Chrome worker per example process, and retains failure traces/screenshots. The sorting smoke suite checks initial rows/state, data regeneration, and inferred sort-direction labels.
- Core type checks run tsc plus a dedicated declaration-emission project, with a fixture exporting inferred sharedTableFeatures. Package build validation also uses publint --strict, separate from runtime assertions.
- PR CI runs affected lint, dependency hygiene, library, type, build-validation, and build targets, and collects core coverage separately. Release CI runs all configured checks before Changesets, but its browser audit depends on the release job and excludes rc.
- Separate workflows validate skill content/snippets, apply formatting, and analyze GitHub Actions with zizmor. Their definitions were inspected only; none establishes an executed result, and several package test scripts explicitly permit no tests.