module-spec 0.1.0 → 0.2.0

package/CHANGELOG.md

@@ -1,7 +1,14 @@
 # Changelog
 
-## Unreleased
+## 0.2.0
 
+- `mutate` counts only the module's core, shell and door tests. An adapter's test and a
+  contract test prove the adapter against the outside and are slow, so a mutant that only
+  they catch now lives until a test through the door catches it. On factory's chat module
+  those tests were 39 of 40 seconds of test time, rerun for every core mutant.
+- Under vitest, `mutate` keeps each module's verdicts in
+  `node_modules/.cache/module-spec/mutate/`, and a rerun tests again only the mutants whose
+  code or covering tests changed.
 - `mutate` changes only `core/`, `shell/` and the door, as the spec says. Before,
   it also changed files in no part, such as an app's `main.ts` or a
   `vitest.config.ts`.

package/lib/languages/typescript/mutate.js

@@ -40,8 +40,19 @@ function runnerConfig(root, tests) {
   };
 }
 
+/**
+ * Under vitest, Stryker keeps each mutant's verdict and the tests that covered it, so a rerun tests again only the
+ * mutants whose code or covering tests changed. The command runner reports no tests, so a weakened test would keep
+ * its old verdict there, and it reruns everything. The file sits under node_modules/.cache, which no project commits.
+ */
+function incrementalConfig(root, module) {
+  if (testRunnerOf(root) !== "vitest") return {};
+  const file = `${module.dir.replaceAll("/", "_")}.json`;
+  return { incremental: true, incrementalFile: path.join(root, "node_modules", ".cache", "module-spec", "mutate", file) };
+}
+
 /** Mutation testing by the kit's own StrykerJS, in a sandbox under the system temp folder. */
-export async function mutate({ root, files, tests }) {
+export async function mutate({ root, module, files, tests }) {
   const work = fs.mkdtempSync(path.join(os.tmpdir(), "module-spec-stryker-"));
   try {
     const report = path.join(work, "report.json");
@@ -58,6 +69,7 @@ export async function mutate({ root, files, tests }) {
       // runners read TypeScript without it, so the rewrite is skipped by naming a file that does not exist.
       tsconfigFile: "module-spec-skips-the-tsconfig-rewrite.json",
       logLevel: "error",
+      ...incrementalConfig(root, module),
     }));
     const dir = kitPackageDir("@stryker-mutator/core");
     const bin = path.join(dir, JSON.parse(fs.readFileSync(path.join(dir, "package.json"), "utf8")).bin.stryker);

package/lib/mutation.js

@@ -15,13 +15,19 @@ export const MUTATION_REPORT = "mutation-report.txt";
  */
 const MUTATED = new Set(["core", "shell"]);
 
-/** The files mutation testing changes in a module, and the module's own tests, which must notice. */
+/**
+ * The files mutation testing changes in a module, and the module's own tests, which must notice. An adapter's test
+ * proves the adapter against the outside and is slow, while the code it reaches is proven through the door, so it
+ * does not count.
+ */
 export function mutationTargets(module) {
   const files = [];
   const tests = [];
   for (const file of module.files) {
     const place = placeOf(module, file);
-    if (place.test) tests.push(file);
+    if (place.test) {
+      if (place.part !== "adapters" && !place.contractTest) tests.push(file);
+    }
     else if (place.door || MUTATED.has(place.part)) files.push(file);
   }
   return { files, tests };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "module-spec",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "How every project splits its code into modules, with the checks that enforce it. The why behind each rule: spec/.",
   "type": "module",
   "packageManager": "pnpm@12.10.1",

package/spec/tests.md

@@ -130,8 +130,10 @@ code does. Mutation testing catches it, because every mutant lives.
   hold only types, not `adapters/`, whose contract tests need the real
   service, and not `view/`, which holds no rules
   ([F3](frontend.md#f3-a-view-holds-no-rules)).
-- **Which tests count:** only the module's own. A mutant that only another
-  module's test catches still lives.
+- **Which tests count:** only the module's own, and not its adapters' tests
+  or contract tests. Those prove an adapter against the outside and are slow.
+  The core they reach is proven through the door. A mutant that only another
+  module's test, or an adapter's test, catches still lives.
 - **Zero live mutants:** `module-spec mutate` fails on any live mutant, and
   names it, even on a module's first run.
 - **When no test can tell:** some mutants behave exactly like the code, such