dev-diagnosis-cli 0.1.5 → 0.1.6

package/CHANGELOG.md

@@ -1,6 +1,17 @@
 # Changelog
 
-## 0.1.5 — unreleased
+## 0.1.6 — unreleased
+
+- Fix: an empty JUnit file (0 bytes, whitespace only, or a declaration/comment
+  and nothing else) no longer parses as a clean run of zero tests — the XML
+  reader now requires a root element, so the file is reported as
+  "no root element", listed in the warnings, and the `flakes` check fails
+  instead of silently reporting on half-read data. A genuinely empty report
+  (`<testsuites></testsuites>`) still parses to zero tests. (62 tests.)
+- Docs: the 0.1.5 entry below is now dated — it went live on npm on
+  2026-11-11 but the entry still said "unreleased".
+
+## 0.1.5 — 2026-11-11
 
 - Fix: a JUnit file that cannot be parsed no longer passes silently —
   `flakes` used to collect the parse error into a warnings list nothing

package/README.md

@@ -107,12 +107,12 @@ Runs the build command twice: cold, with the cache directory moved aside, and wa
 
 ### `flakes` — which tests are flaky
 
-Reads JUnit XML across CI runs — each subdirectory of `<junit-dir>` is one run, and each `*.xml` file directly under it is a run of its own — and ranks tests by instability, using a Wilson 95% lower bound so a test that failed twice in two runs outranks one that failed twice in twenty. It distinguishes *passed-on-retry* (failed then passed in the same run, the classic flake signature) from *always-failing* and plain cross-run flakes, and labels each test `new`, `chronic` or `recovered` from its history. CRLF line endings are normalised before parsing, so Windows-produced XML parses the same as Unix-produced XML.
+Reads JUnit XML across CI runs — each subdirectory of `<junit-dir>` is one run, and each `*.xml` file directly under it is a run of its own — and ranks tests by instability, using a Wilson 95% lower bound so a test that failed twice in two runs outranks one that failed twice in twenty. It distinguishes *passed-on-retry* (failed then passed in the same run, the classic flake signature) from *always-failing* and plain cross-run flakes, and labels each test `new`, `chronic` or `recovered` from its history. CRLF line endings are normalised before parsing, so Windows-produced XML parses the same as Unix-produced XML. A file that cannot be parsed — broken XML, or a file with no root element at all (empty, whitespace-only, a lone declaration) — is printed as a warning and fails the check, so the verdict is never based on half-read data; a genuinely empty report (`<testsuites></testsuites>`) still counts as zero tests.
 
 ## Development
 
 ```sh
-npm test            # node:test, no extra dependencies — 58 tests
+npm test            # node:test, no extra dependencies — 62 tests
 npm run example     # run the CLI against the demo fixture
 ```
 

package/lib/xml.mjs

@@ -165,6 +165,11 @@ export function parseXml(source, options = {}) {
     index = start.end;
   }
   if (stack.length > 1) fail(`unclosed tag <${stack[stack.length - 1].name}>`, length);
+  // An empty document, a file of only whitespace, or a file of only a
+  // declaration/comment is not XML at all: it has no root element, so
+  // treating it as "zero testcases" would silently report a run set as
+  // clean when one of its files was never read.
+  if (!document.children.some((child) => isElement(child))) fail('no root element', length);
   return document;
 }
 

package/package.json

@@ -1 +1 @@
-{"author":"WJDdidi-1","bin":{"dev-diagnosis":"bin/dev-diagnosis.js"},"bugs":{"url":"https://github.com/WJDdidi-1/dev-doctor/issues"},"description":"One offline CLI that diagnoses a repo the way four small tools do: context noise for AI agents, missing CLI commands, build-cache value, and flaky tests.","engines":{"node":">=18"},"files":["bin/","lib/","examples/","README.md","LICENSE","CHANGELOG.md"],"homepage":"https://github.com/WJDdidi-1/dev-doctor#readme","keywords":["cli","diagnostics","ai-coding","context","build-cache","flaky-tests","path","developer-tools","offline"],"license":"Apache-2.0","name":"dev-diagnosis-cli","repository":{"type":"git","url":"git+https://github.com/WJDdidi-1/dev-doctor.git"},"scripts":{"example":"node examples/demo.mjs","test":"node --test"},"type":"module","version":"0.1.5"}
+{"author":"WJDdidi-1","bin":{"dev-diagnosis":"bin/dev-diagnosis.js"},"bugs":{"url":"https://github.com/WJDdidi-1/dev-doctor/issues"},"description":"One offline CLI that diagnoses a repo the way four small tools do: context noise for AI agents, missing CLI commands, build-cache value, and flaky tests.","engines":{"node":">=18"},"files":["bin/","lib/","examples/","README.md","LICENSE","CHANGELOG.md"],"homepage":"https://github.com/WJDdidi-1/dev-doctor#readme","keywords":["cli","diagnostics","ai-coding","context","build-cache","flaky-tests","path","developer-tools","offline"],"license":"Apache-2.0","name":"dev-diagnosis-cli","repository":{"type":"git","url":"git+https://github.com/WJDdidi-1/dev-doctor.git"},"scripts":{"example":"node examples/demo.mjs","test":"node --test"},"type":"module","version":"0.1.6"}