@essential-apps/shopify-test-runner 1.0.14 → 1.0.16

package/src/scripts/runOfflineFullTests.ts

@@ -259,7 +259,7 @@ async function waitForReady(url: string, timeoutMs: number): Promise<void> {
  * Configure the container for offline mode: write Shopify hostname
  * entries into /etc/hosts and install the edge proxy's self-signed
  * cert as a system CA. The container entrypoint
- * (tests/test-offline/docker/entrypoint.sh) does the same thing when
+ * (tests/offline/docker/entrypoint.sh) does the same thing when
  * node_modules is warm at container start; on a cold cache, the
  * entrypoint can't (cert file doesn't exist yet) and this is the
  * post-install backstop.
@@ -589,14 +589,14 @@ async function main(): Promise<void> {
       '[runOfflineFull] FATAL: must run inside the offline container.\n' +
         '  Run: `npm run test:offline-full` (which invokes runDockerOffline.ts)\n' +
         '  If you are seeing this from inside what should be a container, the\n' +
-        "  entrypoint script (tests/test-offline/docker/entrypoint.sh) didn't run or\n" +
+        "  entrypoint script (tests/offline/docker/entrypoint.sh) didn't run or\n" +
         "  didn't export TEST_IN_CONTAINER=true.",
     );
     process.exit(2);
   }
 
   // ── Offline-mode setup (idempotent, survives cold cache) ──
-  // The container entrypoint (tests/test-offline/docker/entrypoint.sh) does
+  // The container entrypoint (tests/offline/docker/entrypoint.sh) does
   // this when node_modules is already populated at container start.
   // But on a FRESH Linux node_modules cache, the entrypoint runs
   // BEFORE `npm install`, so the cert isn't on disk yet and the
@@ -616,10 +616,9 @@ async function main(): Promise<void> {
   // hosts-file redirect. Inside a single network namespace only one
   // bind to :443 wins — N>1 here fails with EADDRINUSE.
   //
-  // For real parallelism, use `runIsolatedDockerOffline.ts` (one
-  // libkrun microVM per test) — each VM has its own network ns so
-  // :443 is per-VM. That's what `npm run test:offline-full:isolated`
-  // invokes; set `TEST_PARALLEL_VMS=N` to scale.
+  // Real parallelism would need one microVM per shard (each with its
+  // own network ns, so :443 is per-VM). That isolated-per-VM runner
+  // is not built today.
   //
   // Set `TEST_OFFLINE_WORKERS=N` (≥2) here only when the supervisor's
   // edge-proxy-per-shard collision is fixed; today it's a footgun.
@@ -643,7 +642,7 @@ async function main(): Promise<void> {
   const scopes = process.env['SCOPES'] ?? 'write_products,read_products,write_discounts,read_discounts';
   const playwrightConfig =
     process.env['TEST_PLAYWRIGHT_CONFIG'] ??
-    'tests/test-offline/playwright.offline-full.config.ts';
+    'tests/offline/playwright.offline-full.config.ts';
   const isChildShard = shardIndex !== null;
   // Backend port: shard k uses BASE + (k-1); single-worker uses BASE.
   const baseBackendPort = Number(process.env['TEST_OFFLINE_BACKEND_PORT'] ?? '8181');
@@ -811,7 +810,7 @@ async function main(): Promise<void> {
   //
   // The browser and Node both reach this proxy at port 443 because
   // the container's `/etc/hosts` maps Shopify hostnames to 127.0.0.1
-  // (kernel-layer DNS rewrite — see tests/test-offline/docker/entrypoint.sh),
+  // (kernel-layer DNS rewrite — see tests/offline/docker/entrypoint.sh),
   // and the edge's self-signed cert is installed as a system CA so
   // TLS validates natively. No Chromium flags or Node monkey-patches
   // required — DNS + TLS work the same way they would against real
@@ -893,7 +892,7 @@ async function main(): Promise<void> {
     // connects locally (via the same neon ws-proxy) and so a real analytics
     // DB is never reachable from an offline run. Harmless for apps without it.
     // The non-prisma tables this client expects are created by the optional
-    // extra-schema hook below (tests/test-offline/offline-extra-schema.sql).
+    // extra-schema hook below (tests/offline/offline-extra-schema.sql).
     ANALYTICS_DATABASE_URL: dbConn,
     // Auth wired to the mock JWT secret — shopify-app-remix uses this
     // to verify session JWTs minted by the mock App Bridge.
@@ -969,13 +968,13 @@ async function main(): Promise<void> {
   // prisma-managed tables; an app may also read a second database with a
   // different ORM (e.g. drizzle for analytics) whose tables prisma doesn't
   // know about. If the consuming app ships
-  // tests/test-offline/offline-extra-schema.sql, apply it to the SAME offline
+  // tests/offline/offline-extra-schema.sql, apply it to the SAME offline
   // Postgres (idempotent CREATE TABLE IF NOT EXISTS), via psql with the
   // MSW-loader-stripped env, exactly like migrate. Skipped if absent, so it's
   // a no-op for apps that don't need it.
-  const extraSchema = resolve(process.cwd(), 'tests/test-offline/offline-extra-schema.sql');
+  const extraSchema = resolve(process.cwd(), 'tests/offline/offline-extra-schema.sql');
   if (existsSync(extraSchema)) {
-    console.log('[runOfflineFull] applying extra schema (tests/test-offline/offline-extra-schema.sql)…');
+    console.log('[runOfflineFull] applying extra schema (tests/offline/offline-extra-schema.sql)…');
     execSync(
       `psql -h ${PG_HOST} -p ${PG_PORT} -d ${dbName} -v ON_ERROR_STOP=1 -f ${JSON.stringify(extraSchema)}`,
       { stdio: 'inherit', env: prismaEnv },

package/src/scripts/runTests.ts

@@ -14,7 +14,7 @@
  * Conventions (overridable via env, but Phase 0 just hardcodes them):
  *   - Backend: `npx vite --port <port> --strictPort --host 0.0.0.0`
  *   - Schema migration: `npx prisma migrate deploy`
- *   - Playwright config at `tests/test-online/playwright.config.ts`
+ *   - Playwright config at `tests/online/playwright.config.ts`
  *   - DB name prefix: derived from the consuming app's package name
  *
  * Env vars forwarded into the backend process (hermetic — we do NOT
@@ -258,7 +258,7 @@ async function main(): Promise<void> {
     // already in process.env (via the --env-file=.env.test flag on
     // the runner).
     const playwrightConfig =
-      process.env['TEST_PLAYWRIGHT_CONFIG'] ?? 'tests/test-online/playwright.config.ts';
+      process.env['TEST_PLAYWRIGHT_CONFIG'] ?? 'tests/online/playwright.config.ts';
     // PLAYWRIGHT_GREP narrows the run to tests matching a regex
     // (Playwright's --grep). Documented as the env-var entry point in
     // runOffline.ts; mirror it here so the vm path

package/src/scripts/runVm.ts

@@ -16,7 +16,7 @@
  *
  * Architecture:
  *   - Image: `essential-apps/shopify-test-vm:latest` baked
- *     via `tests/test-offline/docker/Dockerfile.vm` in the consuming
+ *     via `tests/offline/docker/Dockerfile.vm` in the consuming
  *     app (the equivalent of `Dockerfile` for libkrun). Auto-saved as
  *     a local OCI archive on first invocation via `prepareOciArchive`.
  *   - Bind mounts (virtio-fs DAX):

package/src/scripts/verifyContracts.ts

@@ -2,7 +2,7 @@
 /**
  * verifyContracts — the offline-side conformance check.
  *
- * Reads every vendored contract under `tests/test-offline/contracts/<api>/`,
+ * Reads every vendored contract under `tests/offline/contracts/<api>/`,
  * re-runs its operation against an in-process offline mock with the
  * vendored `variables`, and asserts the response equals the
  * vendored `response`. Any drift fails the check.
@@ -67,7 +67,7 @@ function parseArgs(): Args {
     }
   }
   if (!out.contractsDir) {
-    out.contractsDir = resolve(out.cwd, 'tests/test-offline/contracts', out.api);
+    out.contractsDir = resolve(out.cwd, 'tests/offline/contracts', out.api);
   } else {
     out.contractsDir = resolve(out.cwd, out.contractsDir);
   }

package/src/scripts/verifyRestContracts.ts

@@ -53,7 +53,7 @@ function parseArgs(): Args {
     }
   }
   if (!out.contractsDir) {
-    out.contractsDir = resolve(out.cwd, 'tests/test-offline/contracts/admin-rest');
+    out.contractsDir = resolve(out.cwd, 'tests/offline/contracts/admin-rest');
   } else {
     out.contractsDir = resolve(out.cwd, out.contractsDir);
   }