@openwop/openwop-conformance 2.37.0 → 2.38.0

package/dist/lib/scenario-disposition.js

@@ -110,9 +110,13 @@ export function resolveItRecord(state, assertionCalls, gate, noted, firstError,
  * closed), none an optional extra. Scoped to major 2 because the 146 v1-side
  * sites were not measured and v1 bundles are read through its EOS.
  */
-blockedStands = false) {
-    if (state === 'fail')
-        return { disposition: 'executed-fail', detail: `the test executed and failed: ${(firstError ?? 'no message').slice(0, 300)}` };
+blockedStands = false, 
+/** The `it` title, so a failed row says WHICH leg of the requirement failed. */
+testName) {
+    if (state === 'fail') {
+        const where = testName === undefined || testName.trim() === '' ? '' : ` in "${testName.slice(0, 120)}"`;
+        return { disposition: 'executed-fail', detail: `the test executed and failed${where}: ${(firstError ?? 'no message').slice(0, 300)}` };
+    }
     if (state === 'pass' && assertionCalls > 0) {
         // `blockedDespiteAssertions` (soft-skip.ts): the leg says its setup
         // assertions are not the requirement, and the requirement went unobserved.
@@ -138,11 +142,34 @@ blockedStands = false) {
         return { disposition: 'blocked', detail: 'unclassified return: the test passed with zero assertions and recorded no reason — RFC 0148 §A resolves it to blocked, never to a pass' };
     return { disposition: 'skipped', detail: 'vitest skipped the test (ctx.skip / it.skip) without a recorded gate reason' };
 }
+/**
+ * The `executed-fail` detail for a file row: WHICH cases failed, and what the
+ * first one said.
+ *
+ * Until 2.37.0 this was the fixed string "one or more assertions in the file
+ * failed". A tier-2 host read exactly that for `v2-run-bulk-cancel` — 10
+ * assertions, no case name, no message, and nothing else in the record for that
+ * file — and had to hand-probe every assertion in the file against production to
+ * find out what had happened. A bundle row whose only detail is that sentence is
+ * undiagnosable by construction, and every future flicker in any scenario had
+ * the same problem.
+ */
+export function failureDetail(failures, failedCount) {
+    if (failures.length === 0) {
+        return `${failedCount} test(s) in the file failed; the runner captured no message`;
+    }
+    const head = failures[0];
+    const named = failures.slice(0, 3).map((f) => `"${f.name.slice(0, 120)}"`).join(', ');
+    const more = failures.length > 3 ? ` (+${failures.length - 3} more)` : '';
+    const msg = head.message === undefined || head.message.trim() === '' ? 'no message' : head.message.slice(0, 400);
+    return `${failures.length} test(s) failed — ${named}${more}; first failure: ${msg}`;
+}
 /** Worker half: fold a file's per-test states (+ any gate-recorded reason) into
  *  the ONE disposition the file records. */
-export function fileDisposition(states, gateReason, assertionCount) {
-    if (states.some((s) => s === 'fail'))
-        return { disposition: 'executed-fail', detail: 'one or more assertions in the file failed' };
+export function fileDisposition(states, gateReason, assertionCount, failures = []) {
+    const failed = states.filter((s) => s === 'fail').length;
+    if (failed > 0)
+        return { disposition: 'executed-fail', detail: failureDetail(failures, failed) };
     if (states.some((s) => s === 'pass')) {
         // A test that early-returned through `behaviorGate` is reported by vitest
         // as a pass with zero assertions. When EVERY passing test in the file did
@@ -182,7 +209,9 @@ export function fileDisposition(states, gateReason, assertionCount) {
  *   - every test `ctx.skip()`ped ⇒ the file's noted reason if it wrote one
  *     BEFORE skipping (`ctx.skip()` throws), else `blocked` + the marker.
  */
-export function resolveFileRecord(states, gateReason, assertionCount, noted, specCoherenceFile) {
+export function resolveFileRecord(states, gateReason, assertionCount, noted, specCoherenceFile, 
+/** The failed cases, so an `executed-fail` row NAMES them (2.37.0). */
+failures = []) {
     // A scenario whose subject is the CORPUS, skipped because the published
     // tarball does not bundle spec/v1/. RFC 0148 §A: `blocked` is defined over
     // ADVERTISED BEHAVIOUR, and there is none here — nothing about the host was
@@ -196,7 +225,7 @@ export function resolveFileRecord(states, gateReason, assertionCount, noted, spe
         && assertionCount === 0) {
         return { disposition: 'inapplicable', detail: SPEC_COHERENCE_DETAIL };
     }
-    let { disposition, detail } = fileDisposition(states, gateReason, assertionCount);
+    let { disposition, detail } = fileDisposition(states, gateReason, assertionCount, failures);
     if (disposition === 'executed-pass' && assertionCount === 0) {
         if (noted !== null) {
             disposition = noted.kind;

package/dist/spec-artifacts.lock.json

@@ -1,5 +1,5 @@
 {
   "package": "@openwop/spec-artifacts",
-  "version": "2.37.0",
-  "stampSha256": "7122d36a173c88dfe75b1fd136824e9a3601583b9035916a666b49e11010b77e"
+  "version": "2.38.0",
+  "stampSha256": "ad88f149547eb38bb873fa63e1d18e06e8810e6427d61a72fac94c32c5e28603"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openwop/openwop-conformance",
-  "version": "2.37.0",
+  "version": "2.38.0",
   "description": "Production-ready black-box conformance suite for OpenWOP v1.0 compliant servers.",
   "repository": {
     "type": "git",
@@ -56,6 +56,6 @@
     "@openwop/spec-artifacts": "file:../spec-artifacts"
   },
   "peerDependencies": {
-    "@openwop/spec-artifacts": "2.37.0"
+    "@openwop/spec-artifacts": "2.38.0"
   }
 }