d365fo-mcp 1.16.1 → 1.16.2

package/dist/tools/sdlc/sysTestRunner.js

@@ -1,5 +1,5 @@
 import { execFile } from 'child_process';
-import { parseSysTestXml } from '../../eval/oracle/systest.js';
+import { parseSysTestXml } from './sysTestXml.js';
 import util from 'util';
 import path from 'path';
 import os from 'os';

package/dist/tools/sdlc/sysTestXml.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Reader for the `/xml:` result document SysTestConsole writes.
+ *
+ * This lives beside the runner rather than in `src/eval/` because it is loaded
+ * at runtime by `sysTestRunner.ts`, and `src/eval/**` is a dev-only tree that
+ * package.json's `files` list keeps out of the published tarball
+ * (`"!dist/eval/**"`). A shipped module importing across that boundary makes
+ * the installed server fail to start with ERR_MODULE_NOT_FOUND. The eval
+ * oracle re-exports this from `src/eval/oracle/systest.ts`; the dependency
+ * runs eval → tools, never the other way.
+ */
+/** One test method's outcome, read from the runner's XML result document. */
+export interface SysTestCaseOutcome {
+    name: string;
+    passed: boolean;
+    message?: string;
+}
+/**
+ * Per-method outcomes from the `/xml:` document SysTestConsole writes.
+ *
+ * The shape is the platform's own: SysTestListenerXML builds
+ * `<test-results><results><test-case name="…" success="true|false">` and adds a
+ * `<failure><message>…</message></failure>` child for a failing one (the element
+ * names are #define'd at the top of that class). Reading it beats the regex over
+ * combined stdout that the runner used to classify with: a class named
+ * …ErrorHandlingTest made "error" appear in the output of a passing run, and a
+ * green run was reported as failed.
+ *
+ * Returns [] when the text is not such a document, so callers can fall back.
+ */
+export declare function parseSysTestXml(xml: string | null | undefined): SysTestCaseOutcome[];
+//# sourceMappingURL=sysTestXml.d.ts.map

package/dist/tools/sdlc/sysTestXml.js

@@ -0,0 +1,54 @@
+/**
+ * Reader for the `/xml:` result document SysTestConsole writes.
+ *
+ * This lives beside the runner rather than in `src/eval/` because it is loaded
+ * at runtime by `sysTestRunner.ts`, and `src/eval/**` is a dev-only tree that
+ * package.json's `files` list keeps out of the published tarball
+ * (`"!dist/eval/**"`). A shipped module importing across that boundary makes
+ * the installed server fail to start with ERR_MODULE_NOT_FOUND. The eval
+ * oracle re-exports this from `src/eval/oracle/systest.ts`; the dependency
+ * runs eval → tools, never the other way.
+ */
+/**
+ * Per-method outcomes from the `/xml:` document SysTestConsole writes.
+ *
+ * The shape is the platform's own: SysTestListenerXML builds
+ * `<test-results><results><test-case name="…" success="true|false">` and adds a
+ * `<failure><message>…</message></failure>` child for a failing one (the element
+ * names are #define'd at the top of that class). Reading it beats the regex over
+ * combined stdout that the runner used to classify with: a class named
+ * …ErrorHandlingTest made "error" appear in the output of a passing run, and a
+ * green run was reported as failed.
+ *
+ * Returns [] when the text is not such a document, so callers can fall back.
+ */
+export function parseSysTestXml(xml) {
+    if (!xml || !/<test-case\b/i.test(xml))
+        return [];
+    const outcomes = [];
+    // The SELF-CLOSING form has to be tried first. With the paired form leading, its
+    // `[^>]*` happily consumed the `/` of `<test-case … />` and the lazy body then ran
+    // on to the NEXT `</test-case>`, swallowing two results into one.
+    const caseRe = /<test-case\b([^>]*?)\/>|<test-case\b([^>]*)>([\s\S]*?)<\/test-case>/gi;
+    let m;
+    while ((m = caseRe.exec(xml)) !== null) {
+        const attrs = m[1] ?? m[2] ?? '';
+        const body = m[3] ?? '';
+        const name = /\bname\s*=\s*"([^"]*)"/i.exec(attrs)?.[1] ?? '';
+        const successAttr = /\bsuccess\s*=\s*"([^"]*)"/i.exec(attrs)?.[1];
+        const failure = /<failure\b[^>]*>([\s\S]*?)<\/failure>/i.exec(body)?.[1];
+        const message = failure
+            ? (/<message\b[^>]*>([\s\S]*?)<\/message>/i.exec(failure)?.[1] ?? failure)
+                .replace(/<[^>]+>/g, ' ')
+                .replace(/\s+/g, ' ')
+                .trim()
+            : undefined;
+        // `success` is authoritative when present; a <failure> child decides otherwise.
+        const passed = successAttr !== undefined
+            ? /^(true|1)$/i.test(successAttr)
+            : failure === undefined;
+        outcomes.push(message ? { name, passed, message } : { name, passed });
+    }
+    return outcomes;
+}
+//# sourceMappingURL=sysTestXml.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "d365fo-mcp",
-  "version": "1.16.1",
+  "version": "1.16.2",
   "description": "MCP Server for X++ Code Completion in D365 Finance & Operations",
   "type": "module",
   "main": "dist/index.js",