Marc-André Bombeck 8f90fd3174 Prove the ECG ingest, the dedupe and the migration on dirty data ...

A round trip through the real handlers: post a recording, read it back
through the list and the detail routes, and check what a client actually
receives rather than a fixture rebuilt at each end. Post it twice and
the second call says updated, not inserted, and the table does not grow.
Feed the same strip to the export-archive importer afterwards and it
says skipped; feed it to the importer first and the route says
duplicate. Both directions leave one row.

The migration test drops the index, manufactures the collisions the
resolution step exists for, and runs the migration file through the same
executor the deploy uses. It checks which row survived each tiebreak,
that the salvaged event link followed the keeper, that rows differing
only by user, source or sampling rate were left alone, and that the
constraint rejects a new twin afterwards. Applying the migration to the
empty testcontainer proves none of that.

The Withings ECG tests now hand the transaction the same delegate the
shared writer uses, so they still watch the real write instead of a stub
standing in for it.

2026-08-01 19:26:47 +02:00

..

__tests__

Prove the ECG ingest, the dedupe and the migration on dirty data

2026-08-01 19:26:47 +02:00

persist-recording.ts

Let an Apple Watch ECG arrive without a 1.5 GB export archive

2026-08-01 19:19:01 +02:00