diet-guard/tests/fixtures/kuchnia_credential.json
Krzysztof kuhy Rudnicki 8905d072d0 feat: carry the catering credential to the phone
The Dart half of the credential sync: a `KuchniaCredentialService` that owns
the value locally, a `sync_merge_kuchnia.dart` adapter mirroring the Python
one, and a `_syncKuchniaCredential` tick alongside the banks and budget. The
phone can now receive the panel password, which is the prerequisite for it
fetching anything itself.

One source of truth, per the answered question: the value lives in the synced
document store and nowhere else. Deliberately *not* mirrored into
`flutter_secure_storage` -- two homes for one value is how a stale password
survives a change made on the other device, and the credential has to be
readable synchronously at merge time anyway.

Gated by a second shared fixture, `tests/fixtures/kuchnia_credential.json`,
asserted by both suites. Two cases carry the weight:

- an **unparsable** edit time must fall back to the same clock on both sides
  (Python catches `ValueError` from `fromisoformat`, Dart's `tryParse` returns
  null). Verified they agree on `wall_time_ms == 0`; mutating that expectation
  fails both suites.
- a **blank half** contributes nothing, so a half-filled settings form cannot
  push an empty-string password that wins LWW against a real one.

`KuchniaCredentialService.init()` is called in the WorkManager isolate as well
as `main()`. A fresh isolate has its own static state and `_syncKuchniaCredential`
no-ops when the singleton is missing, so without it a background tick would
neither publish this device's credential nor receive a peer's -- and on the
phone the background tick is most of the syncing there is. Same class of trap
as the `initSyncDeviceId()` one already documented there.

`.toDouble()` came off the bank record: the fields are already `double`, so it
was a no-op the analyzer flags. The field *types* are what keep the encoding
byte-identical to Python's, and `kuchnia_parity_test.dart` asserts that.

654 Dart tests, 1040 Python tests, 100% Python branch coverage.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QQpCiPaSbyRpwsLkH3dgsX
2026-08-23 08:25:27 +02:00

41 lines
1.3 KiB
JSON

{
"_comment": "Shared parity fixture for the catering credential's sync adapter. Read by BOTH diet_guard/tests/test_kuchnia_credential_sync.py and app/test/sync_merge_kuchnia_test.dart. Regenerate with scripts/build_kuchnia_credential_fixture.py.",
"cases": [
{
"edited_at": "2026-08-23T10:00:00+02:00",
"expected_empty": false,
"expected_password": "hunter2",
"expected_username": "me@example.com",
"expected_wall_time_ms": 1787472000000,
"name": "a normal credential",
"password": "hunter2",
"username": "me@example.com"
},
{
"edited_at": "not-a-timestamp",
"expected_empty": false,
"expected_password": "hunter2",
"expected_username": "me@example.com",
"expected_wall_time_ms": 0,
"name": "an unparsable edit time falls back to the epoch",
"password": "hunter2",
"username": "me@example.com"
},
{
"edited_at": "2026-08-23T10:00:00+02:00",
"expected_empty": true,
"name": "a blank password contributes nothing",
"password": "",
"username": "me@example.com"
},
{
"edited_at": "2026-08-23T10:00:00+02:00",
"expected_empty": true,
"name": "a blank username contributes nothing",
"password": "hunter2",
"username": ""
}
],
"device_id": "fixturedev"
}