CodeVetter · Repo Unpack · Testing signals
jasmine/jasmine
Tests and CI definitions were inspected, not executed; no passing result is asserted. Jasmine self-tests with a compiled runner and a separate source implementation, using both component specs and integration specs. The inspected inventory is bounded: configuration and sampled tests establish intended coverage, not exhaustive coverage or successful CI execution.
- The self-test design loads lib as the executing jasmine and source as jasmineUnderTest/privateUnderTest; the contribution guide explicitly warns against leaking implementation-under-test behavior into the executing copy.
- The inspected Node test script loads core and npmPackage specs, checks that requiring jasmine-core creates no globals before installGlobals, maps overallStatus to exit code, and is followed by lint under npm test; it was not executed.
- Browser configuration includes all spec files except npmPackage and source core/HTML factories, while the Node configuration does not select spec/html; browser-only reporting therefore requires the separate browser checks.
- QueueRunner specs exercise delayed promise completion, rejected promises, and conflicting callback/promise declarations using StubPromise, spies, and a mock clock.
- Integration tests check nested-suite execution, hook order, load-time error reporting, and parallelReset removing previous batches while retaining top-level hooks.
- HTML specs inspect initial DOM and progress updates; QueryString and HtmlSpecFilterV2 specs check parameter preservation, URI decoding, exact/prefix paths, and substring filtering. These assertions alone do not establish full page-reload behavior.
- Package specs run npm pack and tar extraction, validate distributed filenames/content boundaries, and clean temporary artifacts; reset is tested in a subprocess. The inspected performance fixture deliberately creates 10,000 passing and 10,000 failing specs, rather than proving a speed threshold.
- Inspected CI definitions schedule Safari on macos-latest with Node 22, and CircleCI Node 20/22/24/26 serial/parallel jobs plus Windows and trusted-branch Sauce browser tests; these definitions were not executed or checked for green runs.