kryptheon 0.1.44 → 0.1.47

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
@@ -225,6 +225,78 @@ is "verification required", ranked HIGH when the value comes from a server
225
225
  response or an error message, MEDIUM when the code alone cannot say. The fix
226
226
  prompt for each one names the file, line and value.
227
227
 
228
+ ## Unusual inputs
229
+
230
+ ```
231
+ npx kryptheon edge
232
+ ```
233
+
234
+ Replays your recorded forms with one field at a time given a value people
235
+ type by accident: nothing, 5000 characters, text with an HTML tag, emoji, a
236
+ negative number, a date that does not exist. It reports only what the run
237
+ proves:
238
+
239
+ - the page threw an error that the plain replay did not;
240
+ - the server answered 5xx where the plain replay did not;
241
+ - the app saved a value it should not take - shown as the field's value in
242
+ the plain replay's request next to the same field in this one, with the
243
+ 2xx answer;
244
+ - a tag typed into a field came back as a real element on the page (the app
245
+ does not escape it).
246
+
247
+ A form that refuses a value is doing its job, so a replay that fails after it
248
+ is said as "held", never as a problem. A "too many requests" (429) answer
249
+ means that value was not tested. A 5xx or page error is run a second time
250
+ before it is called a problem.
251
+
252
+ **It adds test data to your app, and leaves it there.** So it never runs on
253
+ its own - not after a change, not at night - only when you run the command and
254
+ say yes, or press its button in the dashboard. Most of what it types contains
255
+ the word `kryptheon-test`; every write that was accepted is listed at the end.
256
+ It never creates an account, never changes the sign-in, and never prints or
257
+ keeps a password. At most 40 runs per press, with a pause between runs, and
258
+ Stop in the dashboard ends it part way.
259
+
260
+ Run it against your app on your own computer, or your own test copy. `--yes`
261
+ says yes in advance, and only works when every address is on this computer.
262
+ For any other address - including a database your local page saves to, which
263
+ it notices on the first replay - you are warned and must answer yourself.
264
+
265
+ `npx kryptheon recheck <id>` tries a finding's value again: FIXED, or STILL
266
+ OPEN with the new proof.
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
+
228
300
  ## What goes where
229
301
 
230
302
  Only your recordings go in your project, in `tests/`. Everything Kryptheon