ccqa 1.18.0 → 1.20.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/README.md +6 -5
- package/dist/bin/ccqa.mjs +3712 -3400
- package/dist/hub-client/index.d.mts +50 -65
- package/dist/package.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -132,9 +132,9 @@ entry in `.ccqa/config.yaml`. The claim covers those groups too, so
|
|
|
132
132
|
`--concurrency` shortens a run without letting two specs read each other's
|
|
133
133
|
effects, in this run or the next one.
|
|
134
134
|
|
|
135
|
-
When a clean spec still fails, `--on-fail-explain` labels
|
|
136
|
-
|
|
137
|
-
grade the calls on the hub, and it learns from your grades.
|
|
135
|
+
When a clean spec still fails, `--on-fail-explain` labels what has to
|
|
136
|
+
change: `TEST_DRIFT`, `SPEC_CHANGE`, `PRODUCT_BUG`, `ENVIRONMENT`, or
|
|
137
|
+
`UNKNOWN`. You grade the calls on the hub, and it learns from your grades.
|
|
138
138
|
|
|
139
139
|
## In CI
|
|
140
140
|
|
|
@@ -150,8 +150,9 @@ deploy lands
|
|
|
150
150
|
The audit costs cents; a live spec costs dollars. Filtering first leaves
|
|
151
151
|
a run whose failures are worth reading. `deploy record` decides which specs
|
|
152
152
|
the range reaches unless you pass `--no-select-specs`; a range recorded
|
|
153
|
-
without that decision
|
|
154
|
-
hole
|
|
153
|
+
without that decision is assumed reached — a full audit sweep and a full run
|
|
154
|
+
of everything behind it, not a question mark — and nothing fills the hole in
|
|
155
|
+
later.
|
|
155
156
|
|
|
156
157
|
| Job | Trigger | Question it answers |
|
|
157
158
|
|---|---|---|
|