@jskit-ai/database-runtime-postgres 0.1.256 → 0.1.258

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@jskit-ai/database-runtime-postgres",
-  "version": "0.1.256",
+  "version": "0.1.258",
   "type": "module",
   "scripts": {
-    "test": "node --test --test-concurrency=1"
+    "test": "jskit test"
   },
   "exports": {
     "./client": "./src/client/index.js",
@@ -12,11 +12,11 @@
     "./shared/dialect": "./src/shared/dialect.js"
   },
   "dependencies": {
-    "@jskit-ai/database-runtime": "0.1.259",
+    "@jskit-ai/database-runtime": "0.1.261",
     "pg": "^8.13.1"
   },
   "peerDependencies": {
-    "@jskit-ai/kernel": "0.2.10"
+    "@jskit-ai/kernel": "0.2.12"
   },
   "jskit": {
     "kind": "runtime",

package/patterns/postgres-application/PATTERN.md

@@ -53,6 +53,18 @@ dialect. `example/scripts/prepare-database.js` is the portable
 migrate-then-seed entrypoint for managed sessions and deployments.
 `example/.env.example` names the five connection values without a secret.
 
+Tests get their own databases from
+`@jskit-ai/database-runtime/server/testDatabases`. The `test` script runs
+`jskit test --databases`: each Node test file running at once gets a copy of
+`TEST_DB_NAME`, created from `<TEST_DB_NAME>_snapshot`, a database the
+migrations are replayed into once and again only when a migration changes.
+`example/tests/e2e/databases.js` is the browser run's `prepare` module for
+`browserTestConfig({ prepare: "tests/e2e/databases.js" })` from
+`@jskit-ai/jskit-catalog/browser-tests`: each Playwright worker's server gets
+its own seeded copy of `BROWSER_TEST_DB_NAME`. The database user needs
+`CREATEDB`; without it, Node test files run one at a time on the connected
+database.
+
 `example/.github/workflows/verify.yml` is a normal app-owned CI workflow with
 exactly one database service: `postgres` (`postgres:17`, `POSTGRES_*`
 variables, port `5432`, a `pg_isready` health check). Copy it whole from this

package/patterns/postgres-application/example/package.json

@@ -5,9 +5,10 @@
     "db:prepare": "node ./scripts/prepare-database.js",
     "db:migrate": "knex --knexfile ./knexfile.js migrate:latest",
     "db:migrate:rollback": "knex --knexfile ./knexfile.js migrate:rollback",
-    "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list"
+    "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list",
+    "test": "jskit test --databases"
   },
   "dependencies": {
-    "@jskit-ai/database-runtime-postgres": "0.1.256"
+    "@jskit-ai/database-runtime-postgres": "0.1.258"
   }
 }

package/patterns/postgres-application/example/tests/e2e/databases.js

@@ -0,0 +1,25 @@
+import { prepareTestDatabases } from "@jskit-ai/database-runtime/server/testDatabases";
+import knexConfig from "../../knexfile.js";
+
+// The browser run's `prepare` module: `browserTestConfig({ prepare: "tests/e2e/databases.js" })` in
+// playwright.config.mjs runs it once, before the servers start. Every Playwright worker gets its own copy of
+// BROWSER_TEST_DB_NAME (`<name>`, `<name>_1`, ...), created from the snapshot database of the current migrations with
+// CREATE DATABASE ... TEMPLATE, then seeded; the normal and disposable TEST_DB_NAME databases are refused. The database
+// user needs CREATEDB.
+
+/** The fixtures the specs rely on, including any migration-owned baseline rows the app needs. */
+async function seed(transaction) {
+  await transaction("fixtures").insert({ id: 1, label: "Browser fixture" });
+}
+
+export default async function prepareBrowserDatabases({ workers }) {
+  const { databases, summary } = await prepareTestDatabases({
+    knexConfig,
+    environment: process.env,
+    variable: "BROWSER_TEST_DB_NAME",
+    count: workers,
+    seed
+  });
+  console.log(`[browser-tests] ${summary}.`);
+  return databases.map((database) => ({ DB_NAME: database }));
+}