@lariocpt/crust-mongo 0.3.6 → 0.3.7
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/package.json
CHANGED
|
@@ -49,8 +49,9 @@ find this on, and which element":
|
|
|
49
49
|
http://localhost:47831/page-x meta:og:title got "Page X — Real Title" (expected "Page X — Wrong Title")
|
|
50
50
|
```
|
|
51
51
|
|
|
52
|
-
A clean run prints no fix-list section. `--json`
|
|
53
|
-
|
|
52
|
+
A clean run prints no fix-list section on either channel. Under `--json` the
|
|
53
|
+
report owns stdout, so the same table is written to **stderr** (0.3.7) — the
|
|
54
|
+
structured `sources`/`meta` fields carry the same facts for machines.
|
|
54
55
|
|
|
55
56
|
The `detail` prose is unchanged from v0.3.5: the structured fields are purely
|
|
56
57
|
additive.
|
|
@@ -105,6 +106,9 @@ Redirect the whole invocation instead, then judge the report:
|
|
|
105
106
|
crust -c 'verify-web-links --base-url https://example.com --json --no-progress' > report.json
|
|
106
107
|
```
|
|
107
108
|
|
|
109
|
+
The redirect is the artifact; the fix-list arrives on stderr, so the CI log
|
|
110
|
+
still names the broken page and element without a second command.
|
|
111
|
+
|
|
108
112
|
```crust
|
|
109
113
|
read report.json | (s => JSON.parse(s)) | assert (r => r.totals.failures === 0)
|
|
110
114
|
read report.json | (s => JSON.parse(s)) | assert (r => r.totals.complete)
|