spec-controller 0.1.0-alpha.72 → 0.1.0-alpha.74
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/README.md +2 -2
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -66,7 +66,7 @@ A scenario tagged `@unit` names an obligation — a unit test must exist and pas
|
|
|
66
66
|
| `2` | usage — the invocation was wrong |
|
|
67
67
|
| `3` | balanced, but carrying Pending Items, and you asked for `--strict` |
|
|
68
68
|
| `4` | unsound — a proving suite failed to collect, so the ledger could not be trusted to disagree |
|
|
69
|
-
| `5` | nothing to reconcile — no scenario was
|
|
69
|
+
| `5` | nothing to reconcile — no scenario was carried and no evidence was produced, so the run had no basis for a verdict |
|
|
70
70
|
|
|
71
71
|
The whole report is written before the code is set, so a failing run still tells you why.
|
|
72
72
|
|
|
@@ -90,7 +90,7 @@ read-only, a directory, under a regular file or in a directory that does not exi
|
|
|
90
90
|
|
|
91
91
|
**The enumeration is open at the top, and that is the one thing to design your pipeline around.** A
|
|
92
92
|
state that is genuinely none of the above gets a **new** code rather than being folded into the
|
|
93
|
-
nearest one — `5` is the most recent, added when a run over a target that
|
|
93
|
+
nearest one — `5` is the most recent, added when a run over a target that carried no scenario and
|
|
94
94
|
produced nothing was found reporting `0`. So **treat an unrecognised non-zero code as a failure you
|
|
95
95
|
have not seen before**, not as a synonym for `1`. Matching `1` exactly is unaffected by a code being
|
|
96
96
|
added; treating *non-zero* as a red build is already correct, and only imprecise about why.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "spec-controller",
|
|
3
|
-
"version": "0.1.0-alpha.
|
|
3
|
+
"version": "0.1.0-alpha.74",
|
|
4
4
|
"description": "Reconcile the behaviour your scenarios name against the evidence that actually ran — the deterministic `balance` CLI.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"reconciliation",
|
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
"@cucumber/gherkin": "^41.0.0",
|
|
26
26
|
"@cucumber/messages": "^34.0.1",
|
|
27
27
|
"yaml": "^2.9.0",
|
|
28
|
-
"@3f-consulting/spec-controller-core": "0.1.0-alpha.
|
|
28
|
+
"@3f-consulting/spec-controller-core": "0.1.0-alpha.74"
|
|
29
29
|
},
|
|
30
30
|
"publishConfig": {
|
|
31
31
|
"access": "public"
|