ccqa 1.52.0 → 1.53.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/bin/ccqa.mjs +2267 -1451
- package/dist/{evidence-constants-C425F7ZG.mjs → evidence-constants-BLXD0LRY.mjs} +10 -8
- package/dist/{evidence-constants-BufWx8Bt.cjs → evidence-constants-BkPzGtzI.cjs} +10 -8
- package/dist/hub-client/index.d.cts +1 -1
- package/dist/hub-client/index.d.mts +1 -1
- package/dist/package.json +1 -1
- package/dist/runtime/step-evidence.cjs +1 -1
- package/dist/runtime/step-evidence.d.cts +11 -6
- package/dist/runtime/step-evidence.d.mts +11 -6
- package/dist/runtime/step-evidence.mjs +1 -1
- package/dist/runtime/test-helpers.cjs +1 -1
- package/dist/runtime/test-helpers.mjs +1 -1
- package/package.json +1 -1
|
@@ -3,14 +3,16 @@
|
|
|
3
3
|
* Shared constants + helpers for step-boundary evidence: the env var that
|
|
4
4
|
* enables capture, the file-name sanitizer, and the reserved failure ids.
|
|
5
5
|
*
|
|
6
|
-
*
|
|
7
|
-
* / `captureFailureEvidence()` in `test-helpers.ts`
|
|
8
|
-
*
|
|
9
|
-
*
|
|
10
|
-
* `
|
|
11
|
-
*
|
|
12
|
-
*
|
|
13
|
-
*
|
|
6
|
+
* Several producers write the `<id>.png` + `<id>.json` pairs —
|
|
7
|
+
* `abStepEvidence()` / `captureFailureEvidence()` in `test-helpers.ts`
|
|
8
|
+
* (agent-browser replays), `targets/playwright/trace-capture.ts` (frames read
|
|
9
|
+
* out of a run's Playwright trace), and `ccqaStepBefore`/`ccqaStepAfter` in
|
|
10
|
+
* `step-evidence.ts` for tests generated before the capture calls left the
|
|
11
|
+
* committed file — and one consumer reads them back (`loadEvidenceForSpec` in
|
|
12
|
+
* `report/evidence.ts`). They agree only on the contract here, so it is kept
|
|
13
|
+
* under `runtime/` (free of CLI-side imports) so the generated-test modules —
|
|
14
|
+
* imported via `ccqa/test-helpers` and `ccqa/step-evidence` — can share it
|
|
15
|
+
* without dragging the CLI in.
|
|
14
16
|
*/
|
|
15
17
|
/**
|
|
16
18
|
* Env var naming the directory a spec's step evidence is written to. `ccqa
|
|
@@ -3,14 +3,16 @@
|
|
|
3
3
|
* Shared constants + helpers for step-boundary evidence: the env var that
|
|
4
4
|
* enables capture, the file-name sanitizer, and the reserved failure ids.
|
|
5
5
|
*
|
|
6
|
-
*
|
|
7
|
-
* / `captureFailureEvidence()` in `test-helpers.ts`
|
|
8
|
-
*
|
|
9
|
-
*
|
|
10
|
-
* `
|
|
11
|
-
*
|
|
12
|
-
*
|
|
13
|
-
*
|
|
6
|
+
* Several producers write the `<id>.png` + `<id>.json` pairs —
|
|
7
|
+
* `abStepEvidence()` / `captureFailureEvidence()` in `test-helpers.ts`
|
|
8
|
+
* (agent-browser replays), `targets/playwright/trace-capture.ts` (frames read
|
|
9
|
+
* out of a run's Playwright trace), and `ccqaStepBefore`/`ccqaStepAfter` in
|
|
10
|
+
* `step-evidence.ts` for tests generated before the capture calls left the
|
|
11
|
+
* committed file — and one consumer reads them back (`loadEvidenceForSpec` in
|
|
12
|
+
* `report/evidence.ts`). They agree only on the contract here, so it is kept
|
|
13
|
+
* under `runtime/` (free of CLI-side imports) so the generated-test modules —
|
|
14
|
+
* imported via `ccqa/test-helpers` and `ccqa/step-evidence` — can share it
|
|
15
|
+
* without dragging the CLI in.
|
|
14
16
|
*/
|
|
15
17
|
/**
|
|
16
18
|
* Env var naming the directory a spec's step evidence is written to. `ccqa
|
|
@@ -1283,7 +1283,7 @@ interface HubClient {
|
|
|
1283
1283
|
getAttestations(project: string, q: {
|
|
1284
1284
|
profile: string;
|
|
1285
1285
|
}): Promise<AttestationsResponse>;
|
|
1286
|
-
/** Record
|
|
1286
|
+
/** Record a person's judgement that `spec`'s environment failure is resolved. The hub stamps the time and deploy head. */
|
|
1287
1287
|
putAttestation(project: string, q: {
|
|
1288
1288
|
profile: string;
|
|
1289
1289
|
}, body: {
|
|
@@ -1283,7 +1283,7 @@ interface HubClient {
|
|
|
1283
1283
|
getAttestations(project: string, q: {
|
|
1284
1284
|
profile: string;
|
|
1285
1285
|
}): Promise<AttestationsResponse>;
|
|
1286
|
-
/** Record
|
|
1286
|
+
/** Record a person's judgement that `spec`'s environment failure is resolved. The hub stamps the time and deploy head. */
|
|
1287
1287
|
putAttestation(project: string, q: {
|
|
1288
1288
|
profile: string;
|
|
1289
1289
|
}, body: {
|
package/dist/package.json
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
|
|
2
|
-
const require_evidence_constants = require("../evidence-constants-
|
|
2
|
+
const require_evidence_constants = require("../evidence-constants-BkPzGtzI.cjs");
|
|
3
3
|
let node_fs = require("node:fs");
|
|
4
4
|
let node_path = require("node:path");
|
|
5
5
|
//#region src/runtime/step-evidence.ts
|
|
@@ -1,11 +1,16 @@
|
|
|
1
1
|
//#region src/runtime/step-evidence.d.ts
|
|
2
2
|
/**
|
|
3
|
-
* Step-boundary screenshot capture for
|
|
4
|
-
*
|
|
5
|
-
*
|
|
6
|
-
*
|
|
7
|
-
*
|
|
8
|
-
*
|
|
3
|
+
* Step-boundary screenshot capture for a generated Playwright test, kept for
|
|
4
|
+
* the tests that already import it.
|
|
5
|
+
*
|
|
6
|
+
* ccqa no longer emits these calls: a committed spec is plain
|
|
7
|
+
* `@playwright/test`, its steps are `test.step` blocks, and the screenshots
|
|
8
|
+
* are read back out of the run's trace afterwards
|
|
9
|
+
* (`targets/playwright/trace-capture.ts`). The `ccqa/step-evidence` subpath
|
|
10
|
+
* still ships, and `ccqa run` still points `CCQA_EVIDENCE_DIR` at the report,
|
|
11
|
+
* so a spec generated before that change keeps producing its own — higher
|
|
12
|
+
* fidelity — pairs until it is regenerated. Nothing writes new calls to it,
|
|
13
|
+
* and the export goes in a later release.
|
|
9
14
|
*
|
|
10
15
|
* Two constraints shape the whole module:
|
|
11
16
|
*
|
|
@@ -1,11 +1,16 @@
|
|
|
1
1
|
//#region src/runtime/step-evidence.d.ts
|
|
2
2
|
/**
|
|
3
|
-
* Step-boundary screenshot capture for
|
|
4
|
-
*
|
|
5
|
-
*
|
|
6
|
-
*
|
|
7
|
-
*
|
|
8
|
-
*
|
|
3
|
+
* Step-boundary screenshot capture for a generated Playwright test, kept for
|
|
4
|
+
* the tests that already import it.
|
|
5
|
+
*
|
|
6
|
+
* ccqa no longer emits these calls: a committed spec is plain
|
|
7
|
+
* `@playwright/test`, its steps are `test.step` blocks, and the screenshots
|
|
8
|
+
* are read back out of the run's trace afterwards
|
|
9
|
+
* (`targets/playwright/trace-capture.ts`). The `ccqa/step-evidence` subpath
|
|
10
|
+
* still ships, and `ccqa run` still points `CCQA_EVIDENCE_DIR` at the report,
|
|
11
|
+
* so a spec generated before that change keeps producing its own — higher
|
|
12
|
+
* fidelity — pairs until it is regenerated. Nothing writes new calls to it,
|
|
13
|
+
* and the export goes in a later release.
|
|
9
14
|
*
|
|
10
15
|
* Two constraints shape the whole module:
|
|
11
16
|
*
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
import { i as sanitizeStepId, t as EVIDENCE_DIR_ENV } from "../evidence-constants-
|
|
1
|
+
import { i as sanitizeStepId, t as EVIDENCE_DIR_ENV } from "../evidence-constants-BLXD0LRY.mjs";
|
|
2
2
|
import { existsSync, mkdirSync, writeFileSync } from "node:fs";
|
|
3
3
|
import { join } from "node:path";
|
|
4
4
|
//#region src/runtime/step-evidence.ts
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
|
|
2
|
-
const require_evidence_constants = require("../evidence-constants-
|
|
2
|
+
const require_evidence_constants = require("../evidence-constants-BkPzGtzI.cjs");
|
|
3
3
|
let node_fs = require("node:fs");
|
|
4
4
|
let node_path = require("node:path");
|
|
5
5
|
let node_child_process = require("node:child_process");
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
import { i as sanitizeStepId, n as FAILURE_SOURCE, r as FAILURE_STEP_ID, t as EVIDENCE_DIR_ENV } from "../evidence-constants-
|
|
1
|
+
import { i as sanitizeStepId, n as FAILURE_SOURCE, r as FAILURE_STEP_ID, t as EVIDENCE_DIR_ENV } from "../evidence-constants-BLXD0LRY.mjs";
|
|
2
2
|
import { createRequire } from "node:module";
|
|
3
3
|
import { existsSync, mkdirSync, statSync, writeFileSync } from "node:fs";
|
|
4
4
|
import { dirname, isAbsolute, join, resolve } from "node:path";
|