CodeVetter · Repo Unpack · Testing signals
moment/luxon
Tests and CI were inspected, not executed; no passing result or measured coverage is asserted. Jest runs in Node with Babel transformation and coverage collection from source files. Inspected suites cover parsing, DST, localization, duration conversion, interval semantics, and selected fallback behavior. This inventory is bounded: browser rendering, published bundle loading, and release behavior are outside the configured source-test scope.
- Jest searches test/, uses the Node environment and babel-jest, loads setupTests.js, and collects src/**/*.js coverage except src/zone.js; these settings were inspected, not run.
- CI declares Ubuntu jobs on Node 20.20.1, 22.22.1, 24.14.0, and 25.8.1 with LANG=en_US.utf8 and TZ=America/New_York, followed by install, build, format-check, coverage tests, and site generation; execution status was not inspected.
- DST tests distinguish fromObject's current-offset overlap choice from local's cached-offset choice and assert gap bumping, wasHole, and arithmetic across transitions.
- Parsing tests assert ISO offset interpretation versus setZone retention, custom token fields and incompatible-input reasons, reusable-parser equivalence, and locale mismatch errors.
- Formatting tests cover output calendars, numbering-system overrides, IANA/fixed/custom zones, and invalid output; locale-week tests assert differing week starts and year-boundary behavior.
- Duration tests distinguish casual and longterm conversion factors and exercise a custom business-time matrix, including fractional-week conversion into days, hours, and minutes.
- Interval tests cover duration/end alternatives under throwOnInvalid, abbreviated-end inheritance, intersection/merge boundaries, positive-duration splitting, and varying month lengths; two invalid/zero-duration tests also use an already-invalid reversed interval.
- Helpers simulate missing RelativeTimeFormat and locale-week APIs and restore globals; however, Jest's configured roots and coverage targets do not exercise site scripts or build tasks as coverage subjects, and the inspected CI declares no browser test step.