* fix: recurse test discovery so subdir test suites actually run
scripts/run-tests.cjs discovered tests with a flat readdirSync(testDir),
silently excluding tests/observability/ (4 files), tests/dispatch/ (1) and
tests/installer-migrations/ (1) — 94 passing tests — from `npm test` and all
CI lanes. Walk the tree recursively (relative subpaths preserved), classify
suites by basename, and add a fail-on-zero-executed guard for suite/default
runs (escape hatch GSD_ALLOW_EMPTY_SUITE=1) while preserving the empty
--files/--files-from path the CI inert lane relies on.
Unit suite 735 -> 741 files; surfaces ADR-227's observability/dispatch seam.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* test: retire 5 verified-worthless tests
Adversarial verification confirmed these 5 prove nothing — their coverage is
provided more strictly elsewhere:
- enh-2790 'has a name: field' spot-checks (command-contract enforces /^gsd[:-]/)
- command-routing-hub duplicate construct + duplicate ERROR_KINDS assertions
- no-cjs-sdk-handsync-tooling (guarded files that never existed on main; bug-190
covers the real retired SDK artifacts)
- runtime-artifact-layout cline edge case (subsumed by the explicit-global test
and bug-782-cline-skills-emission)
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* test: add ADR-218 release version-validation coverage
ADR-218 (reject leading-zero versions like 1.01.0; npm duplicate pre-check) had
zero tests — the logic lived only in release.yml bash. Add a test that extracts
the actual rejection regexes from the workflow and exercises them against a
boundary table (leading-zero/malformed rejected, valid accepted) plus structural
wiring assertions. Goes red if the regex is reverted to [0-9]+.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* test: redesign weak tests into behavioral, deterministic assertions
Per the ADR test audit, rewrite 27 weak test files (test-only, no source
changes) so each can go red for the defect it guards:
- kill pass-always assert.ok(true) placeholders (research-cli, worktree-baseref,
bug-260 security guard, eslint-rules x24, clusters '|| true')
- replace source-text grep with behavioral calls (install Kilo, sh-hook-paths,
plan-review-convergence) and add a repo-layout governance test
- de-flake real-clock/Math.random coupling (phase last_updated, bug-3707 mtime,
context-utilization property, feat-3594)
- fix independence/shared-state violations (bug-492 singleton, issue-844 tmpRoot,
core reapStaleTempFiles, active-workstream TTY, feat-488 GSD_HOME)
- strengthen property/shape-only tests (research-provider/store classification +
collision) and unconditional plugin.json schema validation (issue-766)
Verified: all 28 files run together 1220 pass / 0 fail / 1 skip.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* chore: add no-tautological-assert lint rule, error in test suite
New custom ESLint rule (eslint-rules/no-tautological-assert.cjs) bans asserts
that can never fail: assert(true)/assert.ok(<always-truthy literal>),
'cond || true' inside an assert, and equality asserts comparing two identical
literals. Wired as error on tests/**; full sweep confirmed zero existing
violations so the suite stays green. Prevents the placeholder-assert regressions
the audit redesigns just removed. RuleTester coverage added (6 valid, 8 invalid).
Note: no-only-tests was already enforced via eslint-plugin-no-only-tests, so no
duplicate rule was added.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* chore: gate new allow-test-rule exemptions to require an issue ref
ADR-456 requires any allow-test-rule exemption added after the ADR to carry a
tracking issue number, but nothing enforced it. New ratchet gate
(scripts/lint-allow-test-rule-refs.cjs, wired into lint:ci) fails when a NEW
allow-test-rule comment lacks a #NNN/URL reference; the 323 existing untracked
exemptions are grandfathered in an allowlist that ratchets down as they gain
refs. Red-green verified (novel untracked offender fails; compliant passes).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* docs: add ADR test-audit evidence report (#1192)
Full risk-first qa-test-architect audit of the ADR portfolio (37 ADRs + 4
platform lenses, adversarial verification of retire verdicts) that drove the
P0 discovery fix, ADR-218 coverage, 5 retires, 27 redesigns, and the two new
lint gates. Filed as point-in-time evidence under docs/issueevidence/, named
for tracking issue #1192.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* test: replace pre-existing raw NUL byte with escape in feat-3594 fixture
feat-3594's null-byte parser fixture contained a literal NUL byte (pre-existing
on next at b10e5681 — confirmed: base blob has 1 NUL, this fix has 0), which
made git treat the file as binary and would break grep/editors. Switch to the
\x00 escape; the runtime string value (a real NUL in the parser input) is
unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* test: address adversarial-review findings
Codex adversarial pass over the branch:
- capability-registry drift test no longer mutates the committed generated
capability-registry.cjs in place (concurrency hazard) — uses in-memory
checkPipeline comparison instead.
- allow-test-rule ratchet now detects exemptions in ALL comment forms (block
/* */ too, matching no-source-grep) so a block comment can't bypass it;
one newly-surfaced pre-existing offender grandfathered (323->324).
- install.test Kilo case asserts on what install(false,'kilo') actually writes
rather than manually calling configureKiloPermissions (masked the call site).
- issue-766 drops the undeclared transitive ajv dep for explicit structural
assertions from the schema fixture.
- adr-218 test notes the hotfix leading-zero gap is tracked in #1186.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* fix: address code-review findings (subdir discovery, rule + test gaps)
xhigh code review surfaced 15 confirmed issues, all fixed:
- run-tests.cjs --files now resolves subdir tests by bare basename + handles
Windows backslash paths (ambiguous basenames error clearly).
- affected-tests-lib.cjs listTestFiles made recursive — the targeted CI lane was
silently dropping changed subdir tests (same false-green class the audit fixed).
- no-tautological-assert now catches 'true || cond' and empty []/{} equality.
- verify-test-quality: restore provenance-classification coverage, tighten the
writeFile circular-detection check, guard the module-level file read.
- sh-hook-paths: cover the global-install .sh delegation branch (#2045 guard).
- active-workstream null-guard runs deterministically (no longer skipped on TTY).
- adr-218 structural guards tightened (major/minor leading-zero; needs: membership).
- repo-layout AGENTS.md guard no longer false-alarms on equivalent refactors.
- cross-ai ordering guard fails red when the step is missing.
- issue-766 parses required fields from the schema fixture (auto-enforced).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* test: stub USERPROFILE alongside HOME in feat-488 (Windows parity)
The feat-488 redesign stubbed process.env.HOME but not USERPROFILE; os.homedir()
resolves from USERPROFILE on Windows, so the home stub was not hermetic there —
caught by windows-test-parity-guard (stubsHomeNoUserProfile). Save/set/restore
USERPROFILE symmetrically with HOME (delete-if-originally-undefined).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* chore: reconcile allow-test-rule allowlist after rebase onto next
Rebasing onto current next pulled in merged PR #1170, which added
inventory-headings-countfree.test.cjs (a baseline allow-test-rule exemption) and
deleted inventory-counts.test.cjs. Grandfather the former and prune the latter so
the ratchet matches the merged tree. No new debt from this PR.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
211 lines
7.9 KiB
JavaScript
211 lines
7.9 KiB
JavaScript
'use strict';
|
|
|
|
/**
|
|
* Property-based tests for research-store.cjs
|
|
*
|
|
* Properties tested:
|
|
* (a) researchKey: never throws on arbitrary inputs (optional strings/null/undefined/numbers)
|
|
* (b) researchKey: stable — same input object produces same key on two calls
|
|
* (c) researchKey: collision-resistant — inputs that differ in a normalizable field
|
|
* produce different cache keys (distinct strings after trim/lowercase still hash
|
|
* to distinct keys)
|
|
*
|
|
* Boundary examples:
|
|
* Concrete pairs that MUST NOT collide (ecosystem/library combos, version variants,
|
|
* query differences).
|
|
*/
|
|
|
|
const { describe, test } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fc = require('./helpers/fast-check-setup.cjs');
|
|
|
|
const { researchKey } = require('../gsd-core/bin/lib/research-store.cjs');
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Arbitrary helpers
|
|
// ---------------------------------------------------------------------------
|
|
|
|
const arbitraryField = fc.oneof(
|
|
fc.string(),
|
|
fc.constant(null),
|
|
fc.constant(undefined),
|
|
fc.integer(),
|
|
fc.float({ noNaN: true }),
|
|
fc.boolean()
|
|
);
|
|
|
|
const arbitraryInput = fc.record(
|
|
{
|
|
ecosystem: arbitraryField,
|
|
library: arbitraryField,
|
|
version: arbitraryField,
|
|
query: arbitraryField,
|
|
kind: arbitraryField,
|
|
},
|
|
{ requiredKeys: [] }
|
|
);
|
|
|
|
/**
|
|
* Two distinct non-empty strings that remain distinct after trim + lowercase
|
|
* (i.e. they are not case/whitespace variants of each other).
|
|
*/
|
|
const twoDistinctStrings = fc
|
|
.tuple(
|
|
fc.string({ minLength: 1 }),
|
|
fc.string({ minLength: 1 })
|
|
)
|
|
.filter(([a, b]) => a.trim().toLowerCase() !== b.trim().toLowerCase());
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Property tests
|
|
// ---------------------------------------------------------------------------
|
|
|
|
describe('research-store: researchKey property tests', () => {
|
|
test('property: never throws on arbitrary inputs', () => {
|
|
fc.assert(
|
|
fc.property(arbitraryInput, (input) => {
|
|
assert.doesNotThrow(() => researchKey(input));
|
|
})
|
|
);
|
|
});
|
|
|
|
test('property: stable — same input object produces same key on two calls', () => {
|
|
fc.assert(
|
|
fc.property(arbitraryInput, (input) => {
|
|
const k1 = researchKey(input);
|
|
const k2 = researchKey(input);
|
|
assert.equal(k1, k2);
|
|
})
|
|
);
|
|
});
|
|
|
|
test('property: always returns a 64-char hex string', () => {
|
|
fc.assert(
|
|
fc.property(arbitraryInput, (input) => {
|
|
const k = researchKey(input);
|
|
assert.match(k, /^[0-9a-f]{64}$/);
|
|
})
|
|
);
|
|
});
|
|
|
|
test('property: collision-resistant — inputs differing in ecosystem produce distinct keys', () => {
|
|
// Vary ecosystem only; hold all other fields constant so only ecosystem distinguishes them.
|
|
fc.assert(
|
|
fc.property(
|
|
twoDistinctStrings,
|
|
arbitraryInput,
|
|
([ecoA, ecoB], base) => {
|
|
const inputA = { ...base, ecosystem: ecoA };
|
|
const inputB = { ...base, ecosystem: ecoB };
|
|
assert.notEqual(
|
|
researchKey(inputA),
|
|
researchKey(inputB),
|
|
`ecosystem "${ecoA}" and "${ecoB}" must not collide`
|
|
);
|
|
}
|
|
)
|
|
);
|
|
});
|
|
|
|
test('property: collision-resistant — inputs differing in library produce distinct keys', () => {
|
|
fc.assert(
|
|
fc.property(
|
|
twoDistinctStrings,
|
|
arbitraryInput,
|
|
([libA, libB], base) => {
|
|
const inputA = { ...base, library: libA };
|
|
const inputB = { ...base, library: libB };
|
|
assert.notEqual(
|
|
researchKey(inputA),
|
|
researchKey(inputB),
|
|
`library "${libA}" and "${libB}" must not collide`
|
|
);
|
|
}
|
|
)
|
|
);
|
|
});
|
|
|
|
test('property: collision-resistant — inputs differing in query produce distinct keys', () => {
|
|
fc.assert(
|
|
fc.property(
|
|
twoDistinctStrings,
|
|
arbitraryInput,
|
|
([qA, qB], base) => {
|
|
const inputA = { ...base, query: qA };
|
|
const inputB = { ...base, query: qB };
|
|
assert.notEqual(
|
|
researchKey(inputA),
|
|
researchKey(inputB),
|
|
`query "${qA}" and "${qB}" must not collide`
|
|
);
|
|
}
|
|
)
|
|
);
|
|
});
|
|
});
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Boundary / concrete collision examples
|
|
// ---------------------------------------------------------------------------
|
|
|
|
describe('research-store: researchKey boundary examples', () => {
|
|
// npm/lodash vs npm/react — same ecosystem, different library
|
|
test('boundary: "npm/lodash" and "npm/react" must not collide', () => {
|
|
const lodash = researchKey({ ecosystem: 'npm', library: 'lodash' });
|
|
const react = researchKey({ ecosystem: 'npm', library: 'react' });
|
|
assert.notEqual(lodash, react, '"npm/lodash" and "npm/react" produced the same cache key');
|
|
});
|
|
|
|
// Same library, different ecosystem
|
|
test('boundary: "npm/lodash" and "pypi/lodash" must not collide', () => {
|
|
const npm = researchKey({ ecosystem: 'npm', library: 'lodash' });
|
|
const pypi = researchKey({ ecosystem: 'pypi', library: 'lodash' });
|
|
assert.notEqual(npm, pypi, '"npm/lodash" and "pypi/lodash" produced the same cache key');
|
|
});
|
|
|
|
// Different versions of the same library
|
|
test('boundary: "npm/lodash@4" and "npm/lodash@3" must not collide', () => {
|
|
const v4 = researchKey({ ecosystem: 'npm', library: 'lodash', version: '4' });
|
|
const v3 = researchKey({ ecosystem: 'npm', library: 'lodash', version: '3' });
|
|
assert.notEqual(v4, v3, '"npm/lodash@4" and "npm/lodash@3" produced the same cache key');
|
|
});
|
|
|
|
// Different query for the same library
|
|
test('boundary: same library with different queries must not collide', () => {
|
|
const usage = researchKey({ ecosystem: 'npm', library: 'react', query: 'hooks usage' });
|
|
const migration = researchKey({ ecosystem: 'npm', library: 'react', query: 'migration guide' });
|
|
assert.notEqual(usage, migration, 'react "hooks usage" and "migration guide" queries produced the same cache key');
|
|
});
|
|
|
|
// Different kind for the same library
|
|
test('boundary: same library with different kinds must not collide', () => {
|
|
const api = researchKey({ ecosystem: 'npm', library: 'lodash', kind: 'api' });
|
|
const guide = researchKey({ ecosystem: 'npm', library: 'lodash', kind: 'guide' });
|
|
assert.notEqual(api, guide, 'lodash "api" and "guide" kinds produced the same cache key');
|
|
});
|
|
|
|
// Determinism: researchKey is stable across calls with the same concrete input
|
|
test('boundary: determinism holds for concrete "npm/lodash" input', () => {
|
|
const input = { ecosystem: 'npm', library: 'lodash', version: '4.17.21', query: 'installation', kind: 'api' };
|
|
const k1 = researchKey(input);
|
|
const k2 = researchKey(input);
|
|
assert.equal(k1, k2, '"npm/lodash" key is not stable across two calls');
|
|
assert.match(k1, /^[0-9a-f]{64}$/, '"npm/lodash" key is not a 64-char hex string');
|
|
});
|
|
|
|
// Normalization: case and whitespace variants must NOT collide with the canonical form
|
|
// (because different ecosystems/libraries should be different, but case-only variants
|
|
// are treated as the same lookup key — this tests that normalization is applied)
|
|
test('boundary: case-only variants produce the SAME key (normalization applied)', () => {
|
|
const lower = researchKey({ ecosystem: 'npm', library: 'lodash' });
|
|
const upper = researchKey({ ecosystem: 'NPM', library: 'LODASH' });
|
|
assert.equal(lower, upper, 'case variants of the same library should map to the same cache key after normalization');
|
|
});
|
|
|
|
test('boundary: whitespace-padded inputs produce the SAME key as trimmed inputs', () => {
|
|
const trimmed = researchKey({ ecosystem: 'npm', library: 'react' });
|
|
const padded = researchKey({ ecosystem: ' npm ', library: ' react ' });
|
|
assert.equal(trimmed, padded, 'whitespace-padded inputs should produce the same key as trimmed inputs');
|
|
});
|
|
});
|