test(db): run the places and incoming leg mode suites on the real database module

They reset through resetDatabase and seed through the ORM factories
instead of the SQLite snapshot mock, so they run in the Postgres lane as
well.

The two cases about a NUL byte in a place name move to
places-nul-sqlite.test.ts, listed in SQLITE_ONLY: they pin SQLite's value
quoting, and Postgres text cannot hold U+0000. The control characters
0x01 to 0x1F stay in places.test.ts and run on both engines.
This commit is contained in:
Maurice
2026-11-17 17:44:07 +01:00
parent c51f4f78bb
commit 927fcab67f
6 changed files with 285 additions and 248 deletions
-2
View File
@@ -53,7 +53,6 @@
"tests/e2e/vacay.e2e.test.ts": 1,
"tests/e2e/weather.e2e.test.ts": 1,
"tests/integration/dayReorder.test.ts": 1,
"tests/integration/leg-mode-incoming.test.ts": 1,
"tests/integration/legacy-upgrade-v066.test.ts": 1,
"tests/integration/legacy-upgrade-v082.test.ts": 1,
"tests/integration/legacy-upgrade-v205.test.ts": 1,
@@ -65,7 +64,6 @@
"tests/integration/memories-unified.test.ts": 1,
"tests/integration/oauth-authorize.test.ts": 1,
"tests/integration/oauth.test.ts": 1,
"tests/integration/places.test.ts": 1,
"tests/integration/plugins/boot-registry-order.test.ts": 1,
"tests/integration/plugins/plugin-runtime.test.ts": 1,
"tests/integration/scheduler-gate.test.ts": 1,