CodeVetter · Repo Unpack · Testing signals
d3/d3
Tests are Mocha plus ESLint, two files, no jsdom component suite and no image snapshots. test/d3-test.js checks that the barrel re-exports every dependency symbol except version. test/docs-test.js checks internal markdown links and anchors. CI on Node 20 runs eslint, the mocha suite, the Rollup build, and the docs build. Algorithm correctness is assumed to be tested in the individual d3-* repositories, which are not present here.
- The test script is mocha 'test/**/*-test.js' && eslint src test. Mocha is a devDependency at ^10.3.0. There is no .mocharc; both tests use the default BDD global it(). The only test files are test/d3-test.js and test/docs-test.js.
- d3-test.js covers export parity only. It iterates package.json dependencies, dynamic-imports each package, and asserts every own enumerable export except the property named version is present on the umbrella namespace. It does not call the functions, does not check types, and does not compare behavior with the bundle in dist/.
- docs-test.js covers internal documentation links. It fails when a relative link's pathname does not end in .md, or when the fragment is not in the anchors derived from ATX headers or {#id} markers. Absolute links with a scheme are skipped. HTML comments are removed before scanning, and directories whose names start with a dot (including docs/.vitepress) are not walked.
- Header anchors are computed by stripping characters other than word characters, digits, and whitespace, trimming, collapsing spaces to hyphens, and lower-casing. Explicit anchors match / {#([\w\d-]+)}/. A link to a page with an empty hash is allowed because getAnchors seeds the list with "".
- CI runs eslint twice. The workflow first runs yarn run eslint src test --format=compact after registering .github/eslint.json as an Actions problem matcher, then yarn test runs mocha and eslint again. It then runs yarn prepublishOnly and yarn docs:build, so a docs-build failure blocks the test workflow even though those steps are not unit tests.
- Lint config is split. The root .eslintrc.json extends eslint:recommended with sourceType module and ecmaVersion 8. test/.eslintrc.json uses ecmaVersion 11 and env es6, browser, and mocha so that it, window, and browser globals are defined in tests.
- Nothing in test/ mounts Vue components, loads Rollup output, checks terser reserved names, hits the GitHub or Observable network loaders, or exercises geo, force, shape, or scale behavior. Those behaviors are documented against source files that live in other repositories, for example d3-fetch symbols link to https://github.com/d3/d3-fetch/blob/main/src/.
- docs:build is part of CI, so VitePress compilation, the gallery.data.js network import, and stargazers.data.ts (which throws when CI is set and the GitHub request fails) are exercised on every push and pull request to main, but only as a build, not as assertions.
- There is no coverage tool, no fixture directory, and no visual-regression harness in package.json. CHANGES.md explicitly defers minor and patch notes to GitHub releases and only records major breaking changes, so tests here are not a changelog oracle.