CodeVetter · Repo Unpack · Testing signals
rollup/rollup
Tests and CI were inspected, not executed; their existence establishes intended checks, not passing results. Mocha suites exercise built artifacts through runtime assertions, output comparisons, cache reruns, CLI invocation, and filesystem watching. Browser tests use Node substitutes rather than an actual browser. Inspection was bounded and does not establish exhaustive coverage or whole-repository absences.
- test:only invokes Mocha on test/test.js, which loads misc, function, form, chunking, hashes, sourcemaps, incremental, hooks, config, CLI, and watch suites.
- Function tests import dist/rollup, generate CommonJS, execute outputs with injected assert, and support build/generation/runtime error expectations.
- Form tests compare generated output across six formats and rerun from bundle.cache; repository guidance distinguishes them from tests that execute generated code.
- Browser tests load browser/dist/rollup.browser.js under Node, mock fetch with filesystem reads, and compare output fixtures; they do not run in an actual browser.
- Watch tests assert rebuild event sequences and output values, reject overlapping asynchronous listener handling, and check closeWatcher after a failed run with a pending rerun.
- test:all includes browser, TypeScript, package, and option checks; ci:coverage adds leak checks and covered Mocha execution alongside browser/type checks.
- CI configures Node 18.20.0 and 24 across selected Linux/macOS/Windows targets, excluding Node 18 on Windows ARM; it tests tarball installation and runs test:only.
- CI checks generated converter drift and uploads JavaScript/Rust coverage; a final failure step preserves test failure even though the coverage execution step uses continue-on-error.