Add capture diagnostics and replay fixtures
Add privacy-safe capture diagnostics and sanitized replay fixtures without changing the existing export format, record order, or UID generation.
This commit is contained in:
parent
73bb100cd6
commit
2b33ea63af
11 changed files with 445 additions and 13 deletions
6
tests/fixtures/README.md
vendored
6
tests/fixtures/README.md
vendored
|
|
@ -22,6 +22,12 @@ Do not replace this file with a real `.pcap`, `.flows`, or exported account
|
|||
history. Add new cases by constructing the smallest relevant payload, replacing
|
||||
all timestamps and endpoints, and extending the privacy assertions.
|
||||
|
||||
`synthetic_capture_diagnostics.json` is a smaller replay transcript for failure
|
||||
paths. It deliberately contains a short response and a marker-free response so
|
||||
the debug sidecar's reason codes and privacy contract can be tested without a
|
||||
real capture. Repeated-byte payloads use `payload_byte` plus `payload_length` to
|
||||
keep the fixture readable.
|
||||
|
||||
## Synthetic NTE_Assets fixture
|
||||
|
||||
`nte_assets/` mirrors only the six table paths and English localization file
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue