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.
44 lines
2.6 KiB
JSON
44 lines
2.6 KiB
JSON
{
|
|
"$schema": "./node_modules/@stryker-mutator/core/schema/stryker-schema.json",
|
|
"_comment": "Decision-kernel mutation lane (issue #1415). The mutate list below MUST mirror KERNEL_MODULES in scripts/mutation/modules.ts — scripts/mutation/config.test.ts asserts it. The lane reports scores and never gates on them (#1457), so no `break` threshold may be set here either. Any edit changes the config content hash the report and lane envelope carry, so scores measured before and after are not comparable.",
|
|
"packageManager": "pnpm",
|
|
"tsconfigFile_comment": "Points at a path that does not exist on purpose. Stryker's sandbox rewrites tsconfig `extends`/`references` through the classic TypeScript API, which the repo's TypeScript 7 native package no longer exposes (`ts.parseConfigFileTextToJson is not a function`). Our tsconfig has neither extends nor references, so there is nothing to rewrite — skipping the preprocessor is exact, not a workaround for a real dependency. The behaviour relied on is that the preprocessor no-ops when the file is absent: see packages/core/src/sandbox/ts-config-preprocessor.ts (https://github.com/stryker-mutator/stryker-js/blob/master/packages/core/src/sandbox/ts-config-preprocessor.ts) and https://stryker-mutator.io/docs/stryker-js/configuration/#tsconfigfile-string. Re-check it on every Stryker upgrade: if a future version errors on a missing tsconfig instead, point this at a real, extends-free tsconfig.",
|
|
"tsconfigFile": "tsconfig.stryker-absent.json",
|
|
"plugins_comment": "Named explicitly: the default `@stryker-mutator/*` glob does not resolve under pnpm's non-flat node_modules, so plugin discovery finds no test runner.",
|
|
"plugins": ["@stryker-mutator/vitest-runner"],
|
|
"testRunner": "vitest",
|
|
"vitest": {
|
|
"configFile": "vitest.mutation.config.ts",
|
|
"related": true
|
|
},
|
|
"reporters": ["progress", "clear-text", "json"],
|
|
"jsonReporter": {
|
|
"fileName": ".tmp/mutation/mutation.json"
|
|
},
|
|
"htmlReporter": {
|
|
"fileName": ".tmp/mutation/mutation.html"
|
|
},
|
|
"coverageAnalysis": "perTest",
|
|
"ignoreStatic": true,
|
|
"tempDirName": ".tmp/stryker",
|
|
"cleanTempDir": true,
|
|
"timeoutMS": 20000,
|
|
"timeoutFactor": 2,
|
|
"thresholds": {
|
|
"high": 90,
|
|
"low": 70,
|
|
"break": null
|
|
},
|
|
"mutate": [
|
|
"packages/kernel/src/errors.ts",
|
|
"src/daemon/ref-frame.ts",
|
|
"src/commands/interaction/runtime/settle.ts",
|
|
"src/utils/scroll-edge-state.ts",
|
|
"packages/selectors/src/**/*.ts",
|
|
"!packages/selectors/src/**/*.test.ts",
|
|
"!packages/selectors/src/internal/__tests__/**",
|
|
"packages/ad-script/src/internal/target-annotation-serde.ts",
|
|
"src/snapshot/snapshot-occlusion.ts"
|
|
]
|
|
}
|