CodeVetter · Repo Unpack · Testing signals
chaijs/chai
Tests and CI were inspected, not executed; no passing result or measured coverage is asserted. The configured suites use Mocha for Node and Web Test Runner with Playwright for browsers. Inspected tests exercise interface behavior, error diagnostics, plugin installation, utility registration, configuration, subsets, and cross-realm exceptions. File-selection rules leave some tracked nested tests outside the default suites, and the inventory is bounded rather than exhaustive.
- The inspected scripts define npm test as Node plus browser suites with pretest lint; test-node uses c8 --99 --check-coverage and Mocha with test/bootstrap/index.js over test/*.js. These definitions were not executed.
- globalErr executes a failure callback, optionally rejects Chai implementation stack frames when captureStackTrace is supported, and validates exact messages, regexes, or error-property subsets.
- The three interface suites contain successful assertions and failure checks; expect additionally verifies literal template tags and invalid-property diagnostics, while should installs its prototype interface.
- Plugin tests cover basic, repeated, nested, chained, and detached use calls; utility tests cover target reassignment, selective flag transfer, and addMethod/addProperty/addChainableMethod events.
- Configuration tests back up and restore config per test and inspect proxy enablement, excluded keys, and a custom deepEqual comparator that accepts nearby numbers.
- Subset tests include nested objects, Date mismatch, circular actual objects with finite expected shapes, validator functions, and null/non-object inputs; those examples do not establish behavior for every cyclic expected graph.
- Both default selectors target top-level test/*.js, excluding nested display/type-detect files; browsers additionally exclude virtual-machines.js. That Node-only test uses vm.runInContext to check exceptions from another realm.
- Inspected CI definitions build/test Node 20, 25, and latest, lint on Node 24, and run Chromium/Firefox browser jobs; none of these workflow steps invokes the separate lint:types script.