mirror of
https://github.com/callstack/agent-device.git
synced 2026-09-14 20:06:34 +08:00
Michał Pierzchała
423927fdd8
* chore(mutation): shrink the lane to report-only (#1457, #1781 wave 2) The mutation harness's two real catches (#1474, #1475) both came from humans reading the weekly score report. The ratchet half never operated: the baseline was committed exactly twice (8cce0ef6b,60400d04b), both times with `stableRuns: 0, gating: false`, and was never updated after the very fixes it triggered — the weekly job computed a new baseline and then `git checkout --`d it, uploading a proposal nobody applied in 3+ weeks. A gate nobody arms is harness weight; the report is the part that paid. Deletes ratchet.ts + ratchet.test.ts, mutation-baselines/, and every baseline/graduation/gating path in run.ts (`--update`, `mutation:baseline`). run.ts now exits non-zero only on a harness failure, never on a score. The report renders the per-kernel table (kernel, score, killed, survived, total, timeouts) plus the surviving mutants a strengthening PR works from. Kernel scoping stays: stryker.config.json and KERNEL_MODULES are untouched. * fix(mutation): restore denominator coverage and publish the table before judging the shard set Review of #1828: - `report.test.ts` re-asserts that Ignored/CompileError/RuntimeError leave the denominator — the one behaviour `ratchet.test.ts` covered and nothing replaced. A `tally()` edit that counted tool noise would have deflated every published score with a green `mutation:test`. - `assertShardsCoverModules` now runs after `emit()`, so an incomplete shard set still publishes the kernels that completed instead of only an error string. This makes the workflow comments' claim about the job summary true rather than re-wording them down. * chore(mutation): trigger the affected lane on exactly the paths that can select mutants The PR lane returns an empty matrix unless the diff touches the harness, so the kernel-source and `**/*.test.ts` triggers only bought a 1-4 min no-op job on ~96% of PRs. `on.pull_request.paths` is now exactly `LANE_TOOLING` plus the workflow file, asserted in both directions by workflow.test.ts against the exported constant — a missing path would let a harness change merge unproven, an extra one starts a job that can only answer `[]`. Also drops the workflow header's contradictory scope paragraph: it claimed the lane selects on kernel sources and any test reaching one, which has not been true since the ratchet went. * fix(mutation): score and publish a short shard set before failing on the count The expected-count check ran inside readShardedReports, before anything was summarized, so on the weekly's real `--expect-shards 10` one dead shard threw away the nine that had reported — the earlier reorder only moved the zero-mutants check. The merge now returns the shard count, and both verdicts run after emit() with the same exit code and `score` stage. Regression uses the weekly argument shape (`--expect-shards 10`, one shard present) and asserts the reporting kernel's row reaches stdout while the run still fails.
42 lines
1.6 KiB
TypeScript
42 lines
1.6 KiB
TypeScript
// The Stryker config and the module registry are two views of one scope. If
|
|
// they drift, the weekly sweep silently measures something other than the
|
|
// enumerated decision kernels — the exact failure this lane exists to catch.
|
|
|
|
import assert from 'node:assert/strict';
|
|
import fs from 'node:fs';
|
|
import path from 'node:path';
|
|
import { test } from 'node:test';
|
|
import { fileURLToPath } from 'node:url';
|
|
import { mutateGlobs } from './modules.ts';
|
|
import { configHash } from './run.ts';
|
|
|
|
const repoRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '../..');
|
|
|
|
function readConfig(): Record<string, unknown> {
|
|
const text = fs.readFileSync(path.join(repoRoot, 'stryker.config.json'), 'utf8');
|
|
return JSON.parse(text) as Record<string, unknown>;
|
|
}
|
|
|
|
test('stryker mutate globs mirror the kernel-module registry', () => {
|
|
assert.deepEqual(
|
|
readConfig().mutate,
|
|
mutateGlobs(),
|
|
'stryker.config.json `mutate` drifted from KERNEL_MODULES — update scripts/mutation/modules.ts and the config together.',
|
|
);
|
|
});
|
|
|
|
test('stryker owns no pass/fail threshold — the lane never gates on a score', () => {
|
|
const thresholds = readConfig().thresholds as { break?: number | null } | undefined;
|
|
assert.equal(
|
|
thresholds?.break ?? null,
|
|
null,
|
|
'A Stryker `break` threshold would fail runs on an absolute score; this lane reports scores and never gates on them (#1457).',
|
|
);
|
|
});
|
|
|
|
test('the config content hash is stable and content-addressed', () => {
|
|
assert.equal(configHash('a'), configHash('a'));
|
|
assert.notEqual(configHash('a'), configHash('b'));
|
|
assert.match(configHash('a'), /^sha256:[0-9a-f]{12}$/);
|
|
});
|