18 lines
1.5 KiB
Markdown
18 lines
1.5 KiB
Markdown
# Validation
|
|
|
|
Observed on 2026-10-11 in the original Windows development workspace. These observations describe that installation; they do not certify every command on every machine.
|
|
|
|
| Check | Result | Scope |
|
|
| --- | --- | --- |
|
|
| Portable offline regression suite | 30 tests passed, no failures/errors/skips | Isolated folder, Python `-I`, no adjacent source/assets |
|
|
| Portable contact export | Passed | 313 local contact rows |
|
|
| Portable old-message reading | Passed | 9,741 timestamp records scanned; five oldest records decoded |
|
|
| Portable native cleanup | Passed | Hook removed, handles released, helper unloaded |
|
|
| Deterministic build | Passed | Repeated build produced identical SHA-256 |
|
|
| Message ZIP export before bundling | Passed | 9,740 records, zero decode errors; plaintext verified |
|
|
| Self-message before bundling | Passed | One message sent; ACK 3 and exact persisted plaintext readback |
|
|
|
|
Every CLI help path is covered by regression tests. Synthetic fixtures cover parsing, normalization/search, export contracts, recipient guarding and helper cache integrity. Not every optional or live feature was rerun from the final bundle. Default tests do not send messages, link accounts or run live probes. JavaScript fixture checks can be skipped when Node.js is absent; inspect the report.
|
|
|
|
Run `python whatsapp.py test` for portable checks, or `python -m whatsapp_suite test` for source checks. Use `--help` before explicit live operations. Test reports and export artifacts are generated locally and ignored by Git. Do not commit live test output.
|