kryptheon 0.1.46 → 0.1.48

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 CHANGED
@@ -265,6 +265,38 @@ it notices on the first replay - you are warned and must answer yourself.
265
265
  `npx kryptheon recheck <id>` tries a finding's value again: FIXED, or STILL
266
266
  OPEN with the new proof.
267
267
 
268
+ ## Reliability
269
+
270
+ ```
271
+ npx kryptheon reliability
272
+ ```
273
+
274
+ Asks two questions of your recorded flows:
275
+
276
+ - **Does it work every time?** Each flow is replayed three times. One that
277
+ fails and then works again, with nothing changed, is reported - with the
278
+ failed run as proof. It is called a problem only when your app answered
279
+ differently in the failed run (a 5xx or a page error the good runs did not
280
+ get); without that, the recording's own timing could be the cause, and it
281
+ is said as a thing to check. A flow that fails all three times is broken,
282
+ which `npx kryptheon check` reports. One that works once and then stops is
283
+ a thing to check: the first run's own data may be in the way.
284
+ - **What happens on a double-click?** Each step that saves (Save, Add,
285
+ Create, Submit...) is clicked twice, quickly. When that saves twice - more
286
+ successful POSTs to the same place than one click makes - it is reported
287
+ with both answers, and the two record ids the server named when it names
288
+ them. A server that answers both clicks with the same record saved it once,
289
+ and that is not reported. A double save is tried a second time before it is
290
+ called a problem.
291
+
292
+ Slower networks are not tried yet.
293
+
294
+ Like the input check, **it adds data to your app** - your flows' own saves,
295
+ replayed - and leaves it there. It runs only when you say yes, with the same
296
+ rules: `--yes` only for an app on this computer, at most 40 runs, Stop in the
297
+ dashboard. `npx kryptheon recheck <id>` replays a flaky flow five times (FIXED
298
+ only if all five work), or double-clicks the step again.
299
+
268
300
  ## What goes where
269
301
 
270
302
  Only your recordings go in your project, in `tests/`. Everything Kryptheon