@testspectra/cli 1.1.8-rc.2 → 1.1.8-rc.21

package/templates/default/specs/ApiInterception/TC-0015-mock-server-sent-events/web.test.ts

@@ -1,26 +1,26 @@
-it("Mock a Server-Sent Events (EventSource) stream via the existing network-intercept engine", async () => {
-  await MatchersPage.open("sse");
-
-  // EventSource's initial request is a plain HTTP GET under the hood — CDP's Fetch domain
-  // intercepts it exactly like any other fetch()/XHR request. Fulfilling it with a
-  // text/event-stream body delivers every "data: ...\n\n" block at once; the browser's own
-  // EventSource parser still splits that into individual "message" events and dispatches them
-  // just as it would for a real stream, which is the part this demo actually cares about.
-  //
-  // What this can't fake: `Fetch.fulfillRequest` delivers a complete, connection-closing
-  // response (there's no way to keep it open indefinitely the way a real SSE endpoint would), so
-  // the browser's EventSource treats that closure as a connection error shortly after — the
-  // events still arrive and get processed first, but the app's own "CONNECTED" status flips back
-  // to disconnected right after, same as it would after a real server unexpectedly closed the
-  // connection. So this test verifies the events were received, not that the connection stayed
-  // open — genuinely-persistent SSE isn't something a request/response-shaped mock can simulate.
-  await Spectra.intercept("/api/sse-feed", "GET", {
-    body: 'data: {"text":"hello from mock SSE"}\n\ndata: {"text":"second event"}\n\n',
-    headers: { "Content-Type": "text/event-stream" },
-  });
-
-  await Spectra.get("#sse-connect-btn").click();
-  await Spectra.getAll(".sse-message-item").shouldHaveLength(2);
-  await Spectra.getAll(".sse-message-item").first().shouldContainText("hello from mock SSE");
-  await Spectra.getAll(".sse-message-item").last().shouldContainText("second event");
-});
+it("Mock a Server-Sent Events (EventSource) stream via the existing network-intercept engine", async () => {
+  await MatchersPage.open("sse");
+
+  // EventSource's initial request is a plain HTTP GET under the hood — CDP's Fetch domain
+  // intercepts it exactly like any other fetch()/XHR request. Fulfilling it with a
+  // text/event-stream body delivers every "data: ...\n\n" block at once; the browser's own
+  // EventSource parser still splits that into individual "message" events and dispatches them
+  // just as it would for a real stream, which is the part this demo actually cares about.
+  //
+  // What this can't fake: `Fetch.fulfillRequest` delivers a complete, connection-closing
+  // response (there's no way to keep it open indefinitely the way a real SSE endpoint would), so
+  // the browser's EventSource treats that closure as a connection error shortly after — the
+  // events still arrive and get processed first, but the app's own "CONNECTED" status flips back
+  // to disconnected right after, same as it would after a real server unexpectedly closed the
+  // connection. So this test verifies the events were received, not that the connection stayed
+  // open — genuinely-persistent SSE isn't something a request/response-shaped mock can simulate.
+  await Spectra.intercept("/api/sse-feed", "GET", {
+    body: 'data: {"text":"hello from mock SSE"}\n\ndata: {"text":"second event"}\n\n',
+    headers: { "Content-Type": "text/event-stream" },
+  });
+
+  await Spectra.get("#sse-connect-btn").click();
+  await Spectra.getAll(".sse-message-item").shouldHaveLength(2);
+  await Spectra.getAll(".sse-message-item").first().shouldContainText("hello from mock SSE");
+  await Spectra.getAll(".sse-message-item").last().shouldContainText("second event");
+});

package/templates/default/specs/ApiInterception/TC-0016-bypass-websocket-with-app-level-mock/spec.md

@@ -1,37 +1,37 @@
----
-id: TC-0016-bypass-websocket-with-app-level-mock
-title: Bypass a real WebSocket connection via an app-level test-only mock flag
-priority: Medium
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: automated
-  mobile: unsupported
----
-
-# Bypass a real WebSocket connection via an app-level test-only mock flag
-
-**Why this isn't network-level interception like `Spectra.intercept()`:** a WebSocket connection
-starts as an HTTP `Upgrade` handshake and then becomes a raw bidirectional frame stream — it's
-never a single request/response CDP's `Fetch` domain can fulfill the way it fulfills a normal
-`fetch()`/`XHR`/`EventSource` request. Chrome DevTools Protocol's WebSocket-related events
-(`Network.webSocketCreated`, `webSocketFrameSent`/`webSocketFrameReceived`, etc.) are
-observation-only — CDP has no command that mocks or rewrites a WS frame in flight. This is a
-genuine protocol-level limitation, not a gap in this driver.
-
-The practical workaround, and what this demo shows: the app itself checks for a test-only global
-flag (`window.__mockWebSocketMessages`) and swaps in an in-memory fake socket when present,
-instead of opening a real connection. `Spectra.browser.evaluate()` sets that flag before the app
-connects. This is the same pattern used by Cypress/Playwright test suites for the same reason.
-
-Mobile coverage is `unsupported`: React Native's WebSocket implementation is a native module,
-not a page-context global reachable via a browser-style `evaluate()` call — a mobile equivalent
-would need the RN app's own WebSocket client wrapper to support a comparable test-only bypass.
-
-## Test Steps
-1. Open the WebSocket matcher section
-2. Set the app-level mock flag via browser.evaluate before the app connects
-3. Click the connect button
-4. Assert the connection status displays CONNECTED and two mocked frames render
-5. Click the disconnect button
-6. Assert the connection status displays DISCONNECTED
+---
+id: TC-0016-bypass-websocket-with-app-level-mock
+title: Bypass a real WebSocket connection via an app-level test-only mock flag
+priority: Medium
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: automated
+  mobile: unsupported
+---
+
+# Bypass a real WebSocket connection via an app-level test-only mock flag
+
+**Why this isn't network-level interception like `Spectra.intercept()`:** a WebSocket connection
+starts as an HTTP `Upgrade` handshake and then becomes a raw bidirectional frame stream — it's
+never a single request/response CDP's `Fetch` domain can fulfill the way it fulfills a normal
+`fetch()`/`XHR`/`EventSource` request. Chrome DevTools Protocol's WebSocket-related events
+(`Network.webSocketCreated`, `webSocketFrameSent`/`webSocketFrameReceived`, etc.) are
+observation-only — CDP has no command that mocks or rewrites a WS frame in flight. This is a
+genuine protocol-level limitation, not a gap in this driver.
+
+The practical workaround, and what this demo shows: the app itself checks for a test-only global
+flag (`window.__mockWebSocketMessages`) and swaps in an in-memory fake socket when present,
+instead of opening a real connection. `Spectra.browser.evaluate()` sets that flag before the app
+connects. This is the same pattern used by Cypress/Playwright test suites for the same reason.
+
+Mobile coverage is `unsupported`: React Native's WebSocket implementation is a native module,
+not a page-context global reachable via a browser-style `evaluate()` call — a mobile equivalent
+would need the RN app's own WebSocket client wrapper to support a comparable test-only bypass.
+
+## Test Steps
+1. Open the WebSocket matcher section
+2. Set the app-level mock flag via browser.evaluate before the app connects
+3. Click the connect button
+4. Assert the connection status displays CONNECTED and two mocked frames render
+5. Click the disconnect button
+6. Assert the connection status displays DISCONNECTED

package/templates/default/specs/ApiInterception/TC-0016-bypass-websocket-with-app-level-mock/web.test.ts

@@ -1,21 +1,21 @@
-it("Bypass a real WebSocket connection via an app-level test-only mock flag", async () => {
-  await MatchersPage.open("websocket");
-
-  // Set BEFORE the app opens its connection — the component checks this flag inside its own
-  // connect() handler and, if present, uses an in-memory fake socket instead of a real
-  // `new WebSocket(...)`. This is necessarily app-level, not network-level: see this TC's
-  // spec.md for why CDP has no way to intercept/mock a WebSocket handshake or its frames the
-  // way Spectra.intercept() does for fetch()/XHR/EventSource.
-  await Spectra.browser.evaluate(
-    "window.__mockWebSocketMessages = ['hello from mock WS', 'second frame']",
-  );
-
-  await Spectra.get("#ws-connect-btn").click();
-  await Spectra.get("#ws-connection-status").shouldHaveText("CONNECTED");
-  await Spectra.getAll(".ws-message-item").shouldHaveLength(2);
-  await Spectra.getAll(".ws-message-item").first().shouldContainText("hello from mock WS");
-  await Spectra.getAll(".ws-message-item").last().shouldContainText("second frame");
-
-  await Spectra.get("#ws-disconnect-btn").click();
-  await Spectra.get("#ws-connection-status").shouldHaveText("DISCONNECTED");
-});
+it("Bypass a real WebSocket connection via an app-level test-only mock flag", async () => {
+  await MatchersPage.open("websocket");
+
+  // Set BEFORE the app opens its connection — the component checks this flag inside its own
+  // connect() handler and, if present, uses an in-memory fake socket instead of a real
+  // `new WebSocket(...)`. This is necessarily app-level, not network-level: see this TC's
+  // spec.md for why CDP has no way to intercept/mock a WebSocket handshake or its frames the
+  // way Spectra.intercept() does for fetch()/XHR/EventSource.
+  await Spectra.browser.evaluate(
+    "window.__mockWebSocketMessages = ['hello from mock WS', 'second frame']",
+  );
+
+  await Spectra.get("#ws-connect-btn").click();
+  await Spectra.get("#ws-connection-status").shouldHaveText("CONNECTED");
+  await Spectra.getAll(".ws-message-item").shouldHaveLength(2);
+  await Spectra.getAll(".ws-message-item").first().shouldContainText("hello from mock WS");
+  await Spectra.getAll(".ws-message-item").last().shouldContainText("second frame");
+
+  await Spectra.get("#ws-disconnect-btn").click();
+  await Spectra.get("#ws-connection-status").shouldHaveText("DISCONNECTED");
+});

package/templates/default/specs/ApiInterception/TC-0017-bypass-captcha-with-test-mode-flag/spec.md

@@ -1,29 +1,29 @@
----
-id: TC-0017-bypass-captcha-with-test-mode-flag
-title: Bypass a live reCAPTCHA widget via an app-level test-only flag
-priority: Medium
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: automated
-  mobile: unsupported
----
-
-# Bypass a live reCAPTCHA widget via an app-level test-only flag
-
-Real reCAPTCHA renders inside a cross-origin iframe (`google.com`), which Google explicitly
-discourages driving via browser automation — there's no `Spectra.intercept()`-style network mock
-for a live third-party widget's challenge/response flow. The demo embeds the real widget (site key
-`6LcWK4QtAAAAAAeA8IAN20JceGQ7L-RWE-LfhZnB`) for visual completeness, but the test itself uses the
-same pattern real projects use in CI: an app-level `window.__bypassCaptcha` flag the submit
-handler honors instead of ever attempting to automate the actual challenge.
-
-Mobile coverage is `unsupported`: a native captcha SDK (rather than a page-context script tag)
-would need its own test-only bypass hook, which is outside what a generic web-style demo can show.
-
-## Test Steps
-1. Open the captcha matcher section
-2. Click submit without the bypass flag and assert the widget refuses
-3. Set the app-level bypass flag via browser.evaluate
-4. Click submit again
-5. Assert the submission message indicates the form was bypassed for automated testing
+---
+id: TC-0017-bypass-captcha-with-test-mode-flag
+title: Bypass a live reCAPTCHA widget via an app-level test-only flag
+priority: Medium
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: automated
+  mobile: unsupported
+---
+
+# Bypass a live reCAPTCHA widget via an app-level test-only flag
+
+Real reCAPTCHA renders inside a cross-origin iframe (`google.com`), which Google explicitly
+discourages driving via browser automation — there's no `Spectra.intercept()`-style network mock
+for a live third-party widget's challenge/response flow. The demo embeds the real widget (site key
+`6LcWK4QtAAAAAAeA8IAN20JceGQ7L-RWE-LfhZnB`) for visual completeness, but the test itself uses the
+same pattern real projects use in CI: an app-level `window.__bypassCaptcha` flag the submit
+handler honors instead of ever attempting to automate the actual challenge.
+
+Mobile coverage is `unsupported`: a native captcha SDK (rather than a page-context script tag)
+would need its own test-only bypass hook, which is outside what a generic web-style demo can show.
+
+## Test Steps
+1. Open the captcha matcher section
+2. Click submit without the bypass flag and assert the widget refuses
+3. Set the app-level bypass flag via browser.evaluate
+4. Click submit again
+5. Assert the submission message indicates the form was bypassed for automated testing

package/templates/default/specs/ApiInterception/TC-0017-bypass-captcha-with-test-mode-flag/web.test.ts

@@ -1,16 +1,16 @@
-it("Bypass a live reCAPTCHA widget via an app-level test-only flag", async () => {
-  await MatchersPage.open("captcha");
-
-  // Baseline: without the flag (and no completed challenge), the widget refuses to submit —
-  // proving the success below is specifically driven by the bypass flag, not a stale state.
-  await Spectra.get("#captcha-submit-btn").click();
-  await Spectra.get("#captcha-submit-message").shouldContainText("complete the reCAPTCHA challenge");
-
-  // Set BEFORE submitting — see this TC's spec.md for why this has to be an app-level bypass
-  // rather than a network-level mock (real reCAPTCHA lives in a cross-origin iframe with no
-  // request/response Spectra.intercept() could fulfill).
-  await Spectra.browser.evaluate("window.__bypassCaptcha = true");
-
-  await Spectra.get("#captcha-submit-btn").click();
-  await Spectra.get("#captcha-submit-message").shouldContainText("bypassed for automated test");
-});
+it("Bypass a live reCAPTCHA widget via an app-level test-only flag", async () => {
+  await MatchersPage.open("captcha");
+
+  // Baseline: without the flag (and no completed challenge), the widget refuses to submit —
+  // proving the success below is specifically driven by the bypass flag, not a stale state.
+  await Spectra.get("#captcha-submit-btn").click();
+  await Spectra.get("#captcha-submit-message").shouldContainText("complete the reCAPTCHA challenge");
+
+  // Set BEFORE submitting — see this TC's spec.md for why this has to be an app-level bypass
+  // rather than a network-level mock (real reCAPTCHA lives in a cross-origin iframe with no
+  // request/response Spectra.intercept() could fulfill).
+  await Spectra.browser.evaluate("window.__bypassCaptcha = true");
+
+  await Spectra.get("#captcha-submit-btn").click();
+  await Spectra.get("#captcha-submit-message").shouldContainText("bypassed for automated test");
+});

package/templates/default/specs/ApiInterception/suite.md

@@ -1,10 +1,10 @@
----
-id: suite-api-interception
-name: ApiInterception
-description: REST API network mocking, GET/POST payload interception, and status assertions
-executionOrder: 1.4
-parallel: true
----
-
-# Suite: ApiInterception
-
+---
+id: suite-api-interception
+name: ApiInterception
+description: REST API network mocking, GET/POST payload interception, and status assertions
+executionOrder: 1.4
+parallel: true
+---
+
+# Suite: ApiInterception
+

package/templates/default/specs/ApiSeeding/TC-0014-seed-and-cleanup-via-hooks/common.test.ts

@@ -1,30 +1,30 @@
-// The `before` hook (hooks/before/common.hook.ts) already ran by the time this test body
-// executes — it seeded a post via a real POST to the demo server's self-hosted API and stashed
-// the result on globalThis for this test to read. Cleanup (hooks/after/common.hook.ts) runs
-// after this whole suite finishes, so it can't be observed from inside the suite's own tests —
-// a separate monitoring suite/run would be how a real project verifies cleanup actually happened.
-//
-// Suite-scoped hooks only run when a worker's whole batch is unambiguously scoped to this one
-// suite (e.g. `spectra run specs/ApiSeeding` or targeting this TC directly) — hook functions are
-// process-global singleton slots, not per-test-case, so a worker batch spanning multiple suites
-// has no correct way to scope suite A's hooks to only run around suite A's own tests, and skips
-// suite-level hooks entirely rather than risk applying the wrong suite's hooks to the wrong
-// tests. Running the FULL default template (`spectra run -t web`/`android`, every suite at once)
-// will legitimately fail this specific test for that reason — that's an inherent limitation of
-// the current worker-batching model, not a bug in this demo.
-it("Verify test data seeded by a before hook via the demo server's self-hosted API is available to the test", async () => {
-  const seeding = (globalThis as any).__apiSeeding;
-
-  if (!seeding?.seededPost) {
-    throw new Error("Expected the before hook to have seeded a post onto globalThis.__apiSeeding, found none");
-  }
-  if (typeof seeding.seededPost.id !== "number") {
-    throw new Error(`Expected seeded post to have a numeric id, got ${JSON.stringify(seeding.seededPost.id)}`);
-  }
-  if (seeding.seededPost.title !== "TestSpectra seeded post") {
-    throw new Error(`Expected seeded post title to match, got "${seeding.seededPost.title}"`);
-  }
-  if (seeding.cleanedUp !== false) {
-    throw new Error("Expected cleanedUp to still be false — the after hook hasn't run yet at this point");
-  }
-});
+// The `before` hook (hooks/before/common.hook.ts) already ran by the time this test body
+// executes — it seeded a post via a real POST to the demo server's self-hosted API and stashed
+// the result on globalThis for this test to read. Cleanup (hooks/after/common.hook.ts) runs
+// after this whole suite finishes, so it can't be observed from inside the suite's own tests —
+// a separate monitoring suite/run would be how a real project verifies cleanup actually happened.
+//
+// Suite-scoped hooks only run when a worker's whole batch is unambiguously scoped to this one
+// suite (e.g. `spectra run specs/ApiSeeding` or targeting this TC directly) — hook functions are
+// process-global singleton slots, not per-test-case, so a worker batch spanning multiple suites
+// has no correct way to scope suite A's hooks to only run around suite A's own tests, and skips
+// suite-level hooks entirely rather than risk applying the wrong suite's hooks to the wrong
+// tests. Running the FULL default template (`spectra run -t web`/`android`, every suite at once)
+// will legitimately fail this specific test for that reason — that's an inherent limitation of
+// the current worker-batching model, not a bug in this demo.
+it("Verify test data seeded by a before hook via the demo server's self-hosted API is available to the test", async () => {
+  const seeding = (globalThis as any).__apiSeeding;
+
+  if (!seeding?.seededPost) {
+    throw new Error("Expected the before hook to have seeded a post onto globalThis.__apiSeeding, found none");
+  }
+  if (typeof seeding.seededPost.id !== "number") {
+    throw new Error(`Expected seeded post to have a numeric id, got ${JSON.stringify(seeding.seededPost.id)}`);
+  }
+  if (seeding.seededPost.title !== "TestSpectra seeded post") {
+    throw new Error(`Expected seeded post title to match, got "${seeding.seededPost.title}"`);
+  }
+  if (seeding.cleanedUp !== false) {
+    throw new Error("Expected cleanedUp to still be false — the after hook hasn't run yet at this point");
+  }
+});

package/templates/default/specs/ApiSeeding/TC-0014-seed-and-cleanup-via-hooks/spec.md

@@ -1,23 +1,23 @@
----
-id: TC-0014-seed-and-cleanup-via-hooks
-title: Verify test data seeded by a before hook via the demo server's self-hosted API is available to the test
-priority: Medium
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: automated
-  mobile: automated
----
-
-# Verify test data seeded by a before hook via the demo server's self-hosted API is available to the test
-
-The before hook seeds against the demo server's self-hosted `/api/posts` (POST), and the after
-hook cleans up via DELETE. Because the hooks run on the host worker (not on the device), the demo
-server must be up on the host — run this suite with `--demo` on any platform, e.g.
-`spectra run "specs/ApiSeeding/TC-0014-seed-and-cleanup-via-hooks/common.test.ts" -t android --demo`.
-
-## Test Steps
-1. Before hook seeds a post via a real POST to the demo server's self-hosted API and stashes it on globalThis
-2. Verify the seeded post is present on globalThis
-3. Assert the seeded post has a numeric id and the expected title
-4. Assert cleanup has not yet run (the after hook runs after this suite finishes)
+---
+id: TC-0014-seed-and-cleanup-via-hooks
+title: Verify test data seeded by a before hook via the demo server's self-hosted API is available to the test
+priority: Medium
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: automated
+  mobile: automated
+---
+
+# Verify test data seeded by a before hook via the demo server's self-hosted API is available to the test
+
+The before hook seeds against the demo server's self-hosted `/api/posts` (POST), and the after
+hook cleans up via DELETE. Because the hooks run on the host worker (not on the device), the demo
+server must be up on the host — run this suite with `--demo` on any platform, e.g.
+`spectra run "specs/ApiSeeding/TC-0014-seed-and-cleanup-via-hooks/common.test.ts" -t android --demo`.
+
+## Test Steps
+1. Before hook seeds a post via a real POST to the demo server's self-hosted API and stashes it on globalThis
+2. Verify the seeded post is present on globalThis
+3. Assert the seeded post has a numeric id and the expected title
+4. Assert cleanup has not yet run (the after hook runs after this suite finishes)

package/templates/default/specs/ApiSeeding/hooks/after/common.hook.ts

@@ -1,16 +1,16 @@
-// Suite-level `after` hook — runs once after this suite's tests complete, regardless of whether
-// they passed, so seeded data is always cleaned up rather than leaking into later runs.
-export default async function () {
-  const seeding = (globalThis as any).__apiSeeding;
-  if (!seeding?.seededPost?.id) return;
-
-  const res = await fetch(`http://localhost:5200/api/posts/${seeding.seededPost.id}`, {
-    method: "DELETE",
-  });
-
-  if (!res.ok) {
-    throw new Error(`ApiSeeding after hook: failed to clean up seeded post ${seeding.seededPost.id} (${res.status})`);
-  }
-
-  seeding.cleanedUp = true;
-}
+// Suite-level `after` hook — runs once after this suite's tests complete, regardless of whether
+// they passed, so seeded data is always cleaned up rather than leaking into later runs.
+export default async function () {
+  const seeding = (globalThis as any).__apiSeeding;
+  if (!seeding?.seededPost?.id) return;
+
+  const res = await fetch(`http://localhost:5200/api/posts/${seeding.seededPost.id}`, {
+    method: "DELETE",
+  });
+
+  if (!res.ok) {
+    throw new Error(`ApiSeeding after hook: failed to clean up seeded post ${seeding.seededPost.id} (${res.status})`);
+  }
+
+  seeding.cleanedUp = true;
+}

package/templates/default/specs/ApiSeeding/hooks/before/common.hook.ts

@@ -1,28 +1,28 @@
-// Suite-level `before` hook — runs once before this suite's tests. Hooks run in the same worker
-// process/global scope as the test files, so data seeded here is handed to tests via a plain
-// `globalThis` namespace rather than a return value (hooks don't have a return channel).
-//
-// Seeds against the demo server's own self-hosted API (started with `--demo`) instead of an
-// external public API, so the round trip is deterministic and offline-safe — same seed-in-
-// `before`, clean-up-in-`after` hook mechanics, with a REAL network round trip, just against a
-// server we control. Because the hook runs on the HOST (not the device), this suite needs the
-// demo server up on the host: run it with `--demo` (e.g. `spectra run ... -t android --demo`).
-// Swap the base URL for a real backend's seeding endpoint in an actual project.
-export default async function () {
-  const res = await fetch("http://localhost:5200/api/posts", {
-    method: "POST",
-    headers: { "Content-Type": "application/json; charset=UTF-8" },
-    body: JSON.stringify({
-      title: "TestSpectra seeded post",
-      body: "Created by ApiSeeding's before hook for TC-0014.",
-      userId: 1,
-    }),
-  });
-
-  if (!res.ok) {
-    throw new Error(`ApiSeeding before hook: failed to seed post (${res.status} ${res.statusText})`);
-  }
-
-  const seeded = await res.json();
-  (globalThis as any).__apiSeeding = { seededPost: seeded, cleanedUp: false };
-}
+// Suite-level `before` hook — runs once before this suite's tests. Hooks run in the same worker
+// process/global scope as the test files, so data seeded here is handed to tests via a plain
+// `globalThis` namespace rather than a return value (hooks don't have a return channel).
+//
+// Seeds against the demo server's own self-hosted API (started with `--demo`) instead of an
+// external public API, so the round trip is deterministic and offline-safe — same seed-in-
+// `before`, clean-up-in-`after` hook mechanics, with a REAL network round trip, just against a
+// server we control. Because the hook runs on the HOST (not the device), this suite needs the
+// demo server up on the host: run it with `--demo` (e.g. `spectra run ... -t android --demo`).
+// Swap the base URL for a real backend's seeding endpoint in an actual project.
+export default async function () {
+  const res = await fetch("http://localhost:5200/api/posts", {
+    method: "POST",
+    headers: { "Content-Type": "application/json; charset=UTF-8" },
+    body: JSON.stringify({
+      title: "TestSpectra seeded post",
+      body: "Created by ApiSeeding's before hook for TC-0014.",
+      userId: 1,
+    }),
+  });
+
+  if (!res.ok) {
+    throw new Error(`ApiSeeding before hook: failed to seed post (${res.status} ${res.statusText})`);
+  }
+
+  const seeded = await res.json();
+  (globalThis as any).__apiSeeding = { seededPost: seeded, cleanedUp: false };
+}

package/templates/default/specs/ApiSeeding/suite.md

@@ -1,9 +1,9 @@
----
-id: suite-api-seeding
-name: ApiSeeding
-description: Seeding and cleaning up test data via a real free public API in before/after hooks
-executionOrder: 2.5
-parallel: true
----
-
-# Suite: ApiSeeding
+---
+id: suite-api-seeding
+name: ApiSeeding
+description: Seeding and cleaning up test data via a real free public API in before/after hooks
+executionOrder: 2.5
+parallel: true
+---
+
+# Suite: ApiSeeding

package/templates/default/specs/Authentication/TC-0021-seed-authenticated-session/mobile.test.ts

@@ -1,7 +1,7 @@
-it("Seed an authenticated session via Spectra.seedSession() instead of the real login UI", async () => {
-  // The deep link asks the app to log itself in against a known test account and persist the
-  // result itself — no login form was ever touched.
-  await Spectra.seedSession();
-
-  await AuthPage.statusBadge.shouldHaveText("Authenticated as demo@testspectra.dev");
-});
+it("Seed an authenticated session via Spectra.seedSession() instead of the real login UI", async () => {
+  // The deep link asks the app to log itself in against a known test account and persist the
+  // result itself — no login form was ever touched.
+  await Spectra.seedSession();
+
+  await AuthPage.statusBadge.shouldHaveText("Authenticated as demo@testspectra.dev");
+});

package/templates/default/specs/Authentication/TC-0021-seed-authenticated-session/spec.md

@@ -1,19 +1,19 @@
----
-id: TC-0021-seed-authenticated-session
-title: Seed an authenticated session via Spectra.seedSession() instead of the real login UI
-priority: High
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: automated
-  mobile: automated
----
-
-# Seed an authenticated session via Spectra.seedSession() instead of the real login UI
-
-## Test Steps
-1. Call the `seedSession` support action — logs in via a direct API call instead of walking
-   through a login form (web: host-side `fetch()` + `Spectra.browser.setCookies()` applies the
-   resulting `HttpOnly` cookie to the browser; mobile: a deep link asks the app to log itself in
-   against a known test account and persist the result itself)
-2. Assert the app reflects an authenticated state
+---
+id: TC-0021-seed-authenticated-session
+title: Seed an authenticated session via Spectra.seedSession() instead of the real login UI
+priority: High
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: automated
+  mobile: automated
+---
+
+# Seed an authenticated session via Spectra.seedSession() instead of the real login UI
+
+## Test Steps
+1. Call the `seedSession` support action — logs in via a direct API call instead of walking
+   through a login form (web: host-side `fetch()` + `Spectra.browser.setCookies()` applies the
+   resulting `HttpOnly` cookie to the browser; mobile: a deep link asks the app to log itself in
+   against a known test account and persist the result itself)
+2. Assert the app reflects an authenticated state

package/templates/default/specs/Authentication/TC-0021-seed-authenticated-session/web.test.ts

@@ -1,9 +1,9 @@
-it("Seed an authenticated session via Spectra.seedSession() instead of the real login UI", async () => {
-  // Logs in via a direct host-side API call and applies the resulting HttpOnly cookie straight
-  // to the browser — no login form was ever touched.
-  await Spectra.seedSession();
-
-  await AuthPage.open();
-  await AuthPage.checkStatusButton.click();
-  await AuthPage.statusBadge.shouldHaveText("Authenticated as demo@testspectra.dev");
-});
+it("Seed an authenticated session via Spectra.seedSession() instead of the real login UI", async () => {
+  // Logs in via a direct host-side API call and applies the resulting HttpOnly cookie straight
+  // to the browser — no login form was ever touched.
+  await Spectra.seedSession();
+
+  await AuthPage.open();
+  await AuthPage.checkStatusButton.click();
+  await AuthPage.statusBadge.shouldHaveText("Authenticated as demo@testspectra.dev");
+});

package/templates/default/specs/Authentication/suite.md

@@ -1,9 +1,9 @@
----
-id: suite-authentication
-name: Authentication
-description: Skipping the real login UI by seeding an authenticated session via a direct API call
-executionOrder: 2.6
-parallel: true
----
-
-# Suite: Authentication
+---
+id: suite-authentication
+name: Authentication
+description: Skipping the real login UI by seeding an authenticated session via a direct API call
+executionOrder: 2.6
+parallel: true
+---
+
+# Suite: Authentication

package/templates/default/specs/BrowserContext/TC-0007-title-and-navigation/mobile.test.ts

@@ -1,9 +1,9 @@
-it("Verify page title and sidebar navigation links", async () => {
-  await MatchersPage.open();
-
-  // Navigation sidebar collection verification
-  await NavigationPage.sidebarLinks.shouldHaveLengthGreaterThan(0);
-
-  // Close sidebar drawer
-  await NavigationPage.closeSidebarButton.click();
-});
+it("Verify page title and sidebar navigation links", async () => {
+  await MatchersPage.open();
+
+  // Navigation sidebar collection verification
+  await NavigationPage.sidebarLinks.shouldHaveLengthGreaterThan(0);
+
+  // Close sidebar drawer
+  await NavigationPage.closeSidebarButton.click();
+});