ccqa 1.17.0 → 1.19.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 +10 -3
- package/dist/bin/ccqa.mjs +4083 -3749
- package/dist/hub-client/index.d.mts +40 -61
- package/dist/package.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -125,9 +125,16 @@ run executes it claims its specs, so a cycle that starts before the last one
|
|
|
125
125
|
finishes skips what is already running instead of driving the same flow
|
|
126
126
|
twice.
|
|
127
127
|
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
128
|
+
Specs that write to the same place outside your app — a chat channel, a
|
|
129
|
+
shared inbox — join a
|
|
130
|
+
[`serialGroups`](./docs/targets.md#serialgroups--specs-that-must-not-run-at-the-same-time)
|
|
131
|
+
entry in `.ccqa/config.yaml`. The claim covers those groups too, so
|
|
132
|
+
`--concurrency` shortens a run without letting two specs read each other's
|
|
133
|
+
effects, in this run or the next one.
|
|
134
|
+
|
|
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.
|
|
131
138
|
|
|
132
139
|
## In CI
|
|
133
140
|
|