CodeVetter · Repo Unpack · Testing signals
mobxjs/mobx
Tests and CI were inspected, not executed; no passing result or coverage percentage is asserted. The bounded inspection found Jest/ts-jest suites, React Testing Library integration tests, ESLint RuleTester fixtures, and codemod subprocess tests. Assertions cover important semantics and resource lifecycles, but configured CI steps have limits that require distinguishing script names from effective checks.
- The inspected test configuration uses Jest projects, ts-jest transformation, jsdom, and a development global; coverage collection targets package TypeScript source, without supplying an execution result.
- Core fixtures assert that two writes inside an action produce only the final autorun value, and that AbortSignal disposal prevents subsequent reaction effects, including initial effects for pre-aborted signals.
- Flow tests assert FlowCancellationError rejection and execution of generator finally blocks; toJS tests assert identity preservation across cyclic objects, arrays, and Maps.
- React Suspense fixtures use Testing Library, fake timers, and observer-tree assertions to test abandoned renders, repeated retries, recovery before subscription, and preservation of committed observers during suspended transitions.
- Retention coverage uses forced GC and WeakRef to check collection of the first rendered element tree; it deliberately excludes first-props collection because plain React.memo fails that control assertion. Registry fixtures separately check native/timer cancellation and synchronous registration avoidance.
- The ESLint plugin runs separate ESLint 7 and 9 Jest projects; missing-observer RuleTester fixtures check valid syntax, diagnostics, and exact autofix output. These inspected projects do not establish behavior across every version allowed by its peer range.
- Codemod tests compare applyTransform output with inline snapshots; CLI fixtures write source files and execute subprocesses to check paths containing spaces and mixed TS/TSX parsing, so running these tests would perform filesystem mutations.
- Build/test CI configures Node 24, npm ci --ignore-scripts, lint, build:check, build:test, serial Jest, size reporting, and performance scripts. Coveralls execution/upload are commented out; core Jest discovery selects base tests, and check-size prints measurements without a budget comparison in its inspected run function.