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

package/templates/default/specs/BrowserContext/TC-0007-title-and-navigation/spec.md

@@ -1,17 +1,17 @@
----
-id: TC-0007-title-and-navigation
-title: Verify page title and sidebar navigation links
-priority: High
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: automated
-  mobile: automated
----
-
-# Verify page title and sidebar navigation links
-
-## Test Steps
-1. Open matchers page
-2. Verify browser page title contains TestSpectra
-3. Verify sidebar navigation links length is greater than 0
+---
+id: TC-0007-title-and-navigation
+title: Verify page title and sidebar navigation links
+priority: High
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: automated
+  mobile: automated
+---
+
+# Verify page title and sidebar navigation links
+
+## Test Steps
+1. Open matchers page
+2. Verify browser page title contains TestSpectra
+3. Verify sidebar navigation links length is greater than 0

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

@@ -1,19 +1,19 @@
-it("Verify page title and sidebar navigation links", async () => {
-  await MatchersPage.open();
-
-  // Browser title assertions
-  await Spectra.browser.shouldHaveTitle("TestSpectra — Matchers API Reference");
-  await Spectra.browser.shouldContainTitle("TestSpectra");
-
-  // Browser URL assertions
-  const currentUrl = await browser.getUrl();
-  await Spectra.browser.shouldHaveUrl(currentUrl);
-  await Spectra.browser.shouldContainUrl("localhost:5173");
-
-  // Page lifecycle and console error diagnostics
-  await Spectra.browser.shouldBeLoaded();
-  await Spectra.browser.shouldHaveNoConsoleErrors();
-
-  // Navigation sidebar collection verification
-  await NavigationPage.sidebarLinks.shouldHaveLengthGreaterThan(0);
-});
+it("Verify page title and sidebar navigation links", async () => {
+  await MatchersPage.open();
+
+  // Browser title assertions
+  await Spectra.browser.shouldHaveTitle("TestSpectra — Matchers API Reference");
+  await Spectra.browser.shouldContainTitle("TestSpectra");
+
+  // Browser URL assertions
+  const currentUrl = await browser.getUrl();
+  await Spectra.browser.shouldHaveUrl(currentUrl);
+  await Spectra.browser.shouldContainUrl("localhost:5173");
+
+  // Page lifecycle and console error diagnostics
+  await Spectra.browser.shouldBeLoaded();
+  await Spectra.browser.shouldHaveNoConsoleErrors();
+
+  // Navigation sidebar collection verification
+  await NavigationPage.sidebarLinks.shouldHaveLengthGreaterThan(0);
+});

package/templates/default/specs/BrowserContext/TC-0022-history-navigation/mobile.test.ts

@@ -1,17 +1,17 @@
-it("Navigate browser history with Spectra.back(), forward(), and refresh()", async () => {
-  // Same cold-start race as DeepLink/TC-0018 — wait for the home screen before firing the deep
-  // link so it isn't racing the app's own still-in-progress initial boot.
-  await Spectra.get("~toggle-sidebar-btn").waitForElement(30000);
-
-  await Spectra.navigate("testspectra-demo://deeplink-target");
-  await Spectra.get("~deeplink-target-marker").waitForElement(10000);
-
-  // Spectra.back() on Android presses the hardware back key — distinct from tapping the screen's
-  // own "‹ Back" button (already covered by DeepLink/TC-0018) — and should pop the nav stack back
-  // to Home exactly the same way.
-  await Spectra.back();
-  await Spectra.get("~toggle-sidebar-btn").waitForElement(10000);
-
-  // Spectra.forward()/Spectra.refresh() have no native-app equivalent (no browser history, no
-  // page reload) — they're intentional no-ops on Android, so there's nothing to assert here.
-});
+it("Navigate browser history with Spectra.back(), forward(), and refresh()", async () => {
+  // Same cold-start race as DeepLink/TC-0018 — wait for the home screen before firing the deep
+  // link so it isn't racing the app's own still-in-progress initial boot.
+  await Spectra.get("~toggle-sidebar-btn").waitForElement(30000);
+
+  await Spectra.navigate("testspectra-demo://deeplink-target");
+  await Spectra.get("~deeplink-target-marker").waitForElement(10000);
+
+  // Spectra.back() on Android presses the hardware back key — distinct from tapping the screen's
+  // own "‹ Back" button (already covered by DeepLink/TC-0018) — and should pop the nav stack back
+  // to Home exactly the same way.
+  await Spectra.back();
+  await Spectra.get("~toggle-sidebar-btn").waitForElement(10000);
+
+  // Spectra.forward()/Spectra.refresh() have no native-app equivalent (no browser history, no
+  // page reload) — they're intentional no-ops on Android, so there's nothing to assert here.
+});

package/templates/default/specs/BrowserContext/TC-0022-history-navigation/spec.md

@@ -1,28 +1,28 @@
----
-id: TC-0022-history-navigation
-title: Navigate browser/app history with Spectra.back(), forward(), and refresh()
-priority: Medium
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: automated
-  mobile: automated
----
-
-# Navigate browser/app history with Spectra.back(), forward(), and refresh()
-
-## Test Steps
-
-### Web
-1. Navigate to two distinct real URLs in sequence, each pushing its own genuine browser history
-   entry (this demo app's in-app hash navigation does not — see the test's own comment)
-2. Verify `Spectra.back()` returns to the previously visited URL
-3. Verify `Spectra.forward()` replays the entry just undone
-4. Verify `Spectra.refresh()` reloads the document while the current URL survives
-
-### Mobile
-1. Navigate to a native route via deep link
-2. Verify `Spectra.back()` (Android hardware back key) pops back to the Home screen
-
-`Spectra.forward()`/`Spectra.refresh()` have no native-app equivalent (no browser history, no page
-reload) and are intentional no-ops on Android — only `Spectra.back()` is exercised on mobile.
+---
+id: TC-0022-history-navigation
+title: Navigate browser/app history with Spectra.back(), forward(), and refresh()
+priority: Medium
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: automated
+  mobile: automated
+---
+
+# Navigate browser/app history with Spectra.back(), forward(), and refresh()
+
+## Test Steps
+
+### Web
+1. Navigate to two distinct real URLs in sequence, each pushing its own genuine browser history
+   entry (this demo app's in-app hash navigation does not — see the test's own comment)
+2. Verify `Spectra.back()` returns to the previously visited URL
+3. Verify `Spectra.forward()` replays the entry just undone
+4. Verify `Spectra.refresh()` reloads the document while the current URL survives
+
+### Mobile
+1. Navigate to a native route via deep link
+2. Verify `Spectra.back()` (Android hardware back key) pops back to the Home screen
+
+`Spectra.forward()`/`Spectra.refresh()` have no native-app equivalent (no browser history, no page
+reload) and are intentional no-ops on Android — only `Spectra.back()` is exercised on mobile.

package/templates/default/specs/BrowserContext/TC-0022-history-navigation/web.test.ts

@@ -1,26 +1,26 @@
-it("Navigate browser history with Spectra.back(), forward(), and refresh()", async () => {
-  await MatchersPage.open();
-
-  // This demo app is single-page — its in-app "navigation" (Spectra.navigate("/#section")) only
-  // ever sets window.location.hash, which this browser does not push as a traversable history
-  // entry (history.length never grows), so there is nothing for back()/forward() to jump between.
-  // Two distinct real paths give them something real: Vite's dev server serves the same SPA shell
-  // for any path, but the browser still treats each as its own document and pushes a genuine
-  // history entry — exactly like a real multi-page site would.
-  await Spectra.navigate("/history-nav-a");
-  await Spectra.browser.shouldContainUrl("/history-nav-a");
-
-  await Spectra.navigate("/history-nav-b");
-  await Spectra.browser.shouldContainUrl("/history-nav-b");
-
-  await Spectra.back();
-  await Spectra.browser.shouldContainUrl("/history-nav-a");
-
-  await Spectra.forward();
-  await Spectra.browser.shouldContainUrl("/history-nav-b");
-
-  // The document reloads, but the current URL survives it.
-  await Spectra.refresh();
-  await Spectra.browser.shouldBeLoaded();
-  await Spectra.browser.shouldContainUrl("/history-nav-b");
-});
+it("Navigate browser history with Spectra.back(), forward(), and refresh()", async () => {
+  await MatchersPage.open();
+
+  // This demo app is single-page — its in-app "navigation" (Spectra.navigate("/#section")) only
+  // ever sets window.location.hash, which this browser does not push as a traversable history
+  // entry (history.length never grows), so there is nothing for back()/forward() to jump between.
+  // Two distinct real paths give them something real: Vite's dev server serves the same SPA shell
+  // for any path, but the browser still treats each as its own document and pushes a genuine
+  // history entry — exactly like a real multi-page site would.
+  await Spectra.navigate("/history-nav-a");
+  await Spectra.browser.shouldContainUrl("/history-nav-a");
+
+  await Spectra.navigate("/history-nav-b");
+  await Spectra.browser.shouldContainUrl("/history-nav-b");
+
+  await Spectra.back();
+  await Spectra.browser.shouldContainUrl("/history-nav-a");
+
+  await Spectra.forward();
+  await Spectra.browser.shouldContainUrl("/history-nav-b");
+
+  // The document reloads, but the current URL survives it.
+  await Spectra.refresh();
+  await Spectra.browser.shouldBeLoaded();
+  await Spectra.browser.shouldContainUrl("/history-nav-b");
+});

package/templates/default/specs/ContentMatchers/TC-0005-text-and-values/common.test.ts

@@ -1,26 +1,26 @@
-// A single common.test.ts, not a web.test.ts/mobile.test.ts pair — the orchestrator's test-case
-// discovery recognizes "common" as a platform stem for every target (web, android, ios, mobile),
-// so this one file runs unmodified on all of them. This works here because every Spectra.*
-// command below is genuinely platform-agnostic (the DSL layer has zero platform branching by
-// design) and MatchersPage's selectors are already abstracted per-platform behind identically-
-// named getters — nothing in this specific test depends on a page origin, a native-only gesture,
-// or a browser-chrome-only assertion (see TC-0013's real-network test for a case that CAN'T be
-// shared this way: Android has no implicit page origin to resolve a relative fetch URL against,
-// so the URL itself has to differ per platform even though the commands stay identical).
-it("Verify exact text, substring text, and input values", async () => {
-  await MatchersPage.open("text");
-
-  // Text assertions (positive and negative)
-  await MatchersPage.exactText.shouldHaveText(Fixture.playgroundData.welcomeText);
-  await MatchersPage.exactText.shouldNotHaveText("Unexpected Text");
-
-  await MatchersPage.partialText.shouldContainText("Welcome");
-  await MatchersPage.partialText.shouldNotContainText("Goodbye");
-
-  // Value assertions (positive and negative)
-  await MatchersPage.emailInput.shouldHaveValue(Fixture.playgroundData.defaultEmail);
-  await MatchersPage.emailInput.shouldNotHaveValue("wrong.user@testspectra.dev");
-
-  await MatchersPage.tokenInput.shouldContainValue("JWT_");
-  await MatchersPage.tokenInput.shouldNotContainValue("EXPIRED_SESSION");
-});
+// A single common.test.ts, not a web.test.ts/mobile.test.ts pair — the orchestrator's test-case
+// discovery recognizes "common" as a platform stem for every target (web, android, ios, mobile),
+// so this one file runs unmodified on all of them. This works here because every Spectra.*
+// command below is genuinely platform-agnostic (the DSL layer has zero platform branching by
+// design) and MatchersPage's selectors are already abstracted per-platform behind identically-
+// named getters — nothing in this specific test depends on a page origin, a native-only gesture,
+// or a browser-chrome-only assertion (see TC-0013's real-network test for a case that CAN'T be
+// shared this way: Android has no implicit page origin to resolve a relative fetch URL against,
+// so the URL itself has to differ per platform even though the commands stay identical).
+it("Verify exact text, substring text, and input values", async () => {
+  await MatchersPage.open("text");
+
+  // Text assertions (positive and negative)
+  await MatchersPage.exactText.shouldHaveText(Fixture.playgroundData.welcomeText);
+  await MatchersPage.exactText.shouldNotHaveText("Unexpected Text");
+
+  await MatchersPage.partialText.shouldContainText("Welcome");
+  await MatchersPage.partialText.shouldNotContainText("Goodbye");
+
+  // Value assertions (positive and negative)
+  await MatchersPage.emailInput.shouldHaveValue(Fixture.playgroundData.defaultEmail);
+  await MatchersPage.emailInput.shouldNotHaveValue("wrong.user@testspectra.dev");
+
+  await MatchersPage.tokenInput.shouldContainValue("JWT_");
+  await MatchersPage.tokenInput.shouldNotContainValue("EXPIRED_SESSION");
+});

package/templates/default/specs/ContentMatchers/TC-0005-text-and-values/spec.md

@@ -1,19 +1,19 @@
----
-id: TC-0005-text-and-values
-title: Verify exact text, substring text, and input values
-priority: High
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: automated
-  mobile: automated
----
-
-# Verify exact text, substring text, and input values
-
-## Test Steps
-1. Open text matchers section in matchers page
-2. Verify exact text matches playground welcome text
-3. Verify partial text contains welcome keyword
-4. Verify email input value matches default email
-5. Verify token input value contains JWT prefix
+---
+id: TC-0005-text-and-values
+title: Verify exact text, substring text, and input values
+priority: High
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: automated
+  mobile: automated
+---
+
+# Verify exact text, substring text, and input values
+
+## Test Steps
+1. Open text matchers section in matchers page
+2. Verify exact text matches playground welcome text
+3. Verify partial text contains welcome keyword
+4. Verify email input value matches default email
+5. Verify token input value contains JWT prefix

package/templates/default/specs/ContentMatchers/TC-0006-collections-and-empty/mobile.test.ts

@@ -1,11 +1,11 @@
-it("Verify collection lengths, counts, and empty lists", async () => {
-  await MatchersPage.open("length");
-
-  // Receiver assertion methods
-  await MatchersPage.productCards.shouldHaveLength(4);
-  await MatchersPage.productCards.shouldNotHaveLength(0);
-  await MatchersPage.productCards.shouldHaveLengthGreaterThan(0);
-  await MatchersPage.productCards.shouldHaveLengthLessThan(10);
-  await MatchersPage.emptyList.shouldBeEmpty();
-  await MatchersPage.productCards.shouldNotBeEmpty();
-});
+it("Verify collection lengths, counts, and empty lists", async () => {
+  await MatchersPage.open("length");
+
+  // Receiver assertion methods
+  await MatchersPage.productCards.shouldHaveLength(4);
+  await MatchersPage.productCards.shouldNotHaveLength(0);
+  await MatchersPage.productCards.shouldHaveLengthGreaterThan(0);
+  await MatchersPage.productCards.shouldHaveLengthLessThan(10);
+  await MatchersPage.emptyList.shouldBeEmpty();
+  await MatchersPage.productCards.shouldNotBeEmpty();
+});

package/templates/default/specs/ContentMatchers/TC-0006-collections-and-empty/spec.md

@@ -1,17 +1,17 @@
----
-id: TC-0006-collections-and-empty
-title: Verify collection lengths, counts, and empty lists
-priority: High
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: automated
-  mobile: automated
----
-
-# Verify collection lengths, counts, and empty lists
-
-## Test Steps
-1. Open collection length section in matchers page
-2. Assert product cards count equals 4 and is greater than 0
-3. Assert empty list container is empty
+---
+id: TC-0006-collections-and-empty
+title: Verify collection lengths, counts, and empty lists
+priority: High
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: automated
+  mobile: automated
+---
+
+# Verify collection lengths, counts, and empty lists
+
+## Test Steps
+1. Open collection length section in matchers page
+2. Assert product cards count equals 4 and is greater than 0
+3. Assert empty list container is empty

package/templates/default/specs/ContentMatchers/TC-0006-collections-and-empty/web.test.ts

@@ -1,11 +1,11 @@
-it("Verify collection lengths, counts, and empty lists", async () => {
-  await MatchersPage.open("length");
-
-  // Receiver assertion methods
-  await MatchersPage.productCards.shouldHaveLength(4);
-  await MatchersPage.productCards.shouldNotHaveLength(0);
-  await MatchersPage.productCards.shouldHaveLengthGreaterThan(0);
-  await MatchersPage.productCards.shouldHaveLengthLessThan(10);
-  await MatchersPage.emptyList.shouldBeEmpty();
-  await MatchersPage.productCards.shouldNotBeEmpty();
-});
+it("Verify collection lengths, counts, and empty lists", async () => {
+  await MatchersPage.open("length");
+
+  // Receiver assertion methods
+  await MatchersPage.productCards.shouldHaveLength(4);
+  await MatchersPage.productCards.shouldNotHaveLength(0);
+  await MatchersPage.productCards.shouldHaveLengthGreaterThan(0);
+  await MatchersPage.productCards.shouldHaveLengthLessThan(10);
+  await MatchersPage.emptyList.shouldBeEmpty();
+  await MatchersPage.productCards.shouldNotBeEmpty();
+});

package/templates/default/specs/ContentMatchers/TC-0020-scoped-element-access/common.test.ts

@@ -1,14 +1,14 @@
-it("element.get()/getAll() resolves a child scoped to its parent's own subtree", async () => {
-  await MatchersPage.open();
-  await MatchersPage.overviewSection.shouldBeVisible();
-
-  // Positive: the subtitle is a real descendant of the overview section, so the scoped lookup
-  // resolves it.
-  await MatchersPage.overviewSubtitle().shouldExist();
-
-  // Negative (the actual scoping proof): the submit button lives in a different section
-  // entirely. If .get() weren't genuinely scoped (e.g. silently fell back to a page-wide
-  // lookup), this would incorrectly resolve to the globally-existing element instead of
-  // correctly not finding it.
-  await MatchersPage.overviewOutsideElement().shouldNotExist();
-});
+it("element.get()/getAll() resolves a child scoped to its parent's own subtree", async () => {
+  await MatchersPage.open();
+  await MatchersPage.overviewSection.shouldBeVisible();
+
+  // Positive: the subtitle is a real descendant of the overview section, so the scoped lookup
+  // resolves it.
+  await MatchersPage.overviewSubtitle().shouldExist();
+
+  // Negative (the actual scoping proof): the submit button lives in a different section
+  // entirely. If .get() weren't genuinely scoped (e.g. silently fell back to a page-wide
+  // lookup), this would incorrectly resolve to the globally-existing element instead of
+  // correctly not finding it.
+  await MatchersPage.overviewOutsideElement().shouldNotExist();
+});

package/templates/default/specs/ContentMatchers/TC-0020-scoped-element-access/spec.md

@@ -1,21 +1,21 @@
----
-id: TC-0020-scoped-element-access
-title: element.get()/getAll() resolves a child scoped to its parent's own subtree
-priority: High
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: automated
-  mobile: automated
----
-
-# element.get()/getAll() resolves a child scoped to its parent's own subtree
-
-## Test Steps
-1. Open the matchers page and assert the overview section is visible
-2. From the overview section, resolve the page subtitle via `.get()` and assert it exists — the
-   subtitle is a real descendant, so the scoped lookup finds it
-3. From the same overview section, resolve the submit button via `.get()` and assert it does NOT
-   exist — the submit button lives in a different section entirely, so this only passes if the
-   lookup is genuinely scoped to overview's own subtree rather than silently falling back to a
-   page-wide match
+---
+id: TC-0020-scoped-element-access
+title: element.get()/getAll() resolves a child scoped to its parent's own subtree
+priority: High
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: automated
+  mobile: automated
+---
+
+# element.get()/getAll() resolves a child scoped to its parent's own subtree
+
+## Test Steps
+1. Open the matchers page and assert the overview section is visible
+2. From the overview section, resolve the page subtitle via `.get()` and assert it exists — the
+   subtitle is a real descendant, so the scoped lookup finds it
+3. From the same overview section, resolve the submit button via `.get()` and assert it does NOT
+   exist — the submit button lives in a different section entirely, so this only passes if the
+   lookup is genuinely scoped to overview's own subtree rather than silently falling back to a
+   page-wide match

package/templates/default/specs/DeepLink/TC-0018-navigate-via-deep-link/mobile.test.ts

@@ -1,28 +1,28 @@
-it("Navigate directly to a native route via Spectra.navigate() and an Android deep link", async () => {
-  // The orchestrator's own bootstrap launches the app (fire-and-forget, ~1.5s wait) before any
-  // test code runs at all — other tests never notice because their first action is a click()
-  // with its own generous poll budget, which absorbs whatever's left of the cold start. This
-  // test's first action is Spectra.navigate() itself, which is also fire-and-forget and has no
-  // such budget, so without this it races the deep-link intent against the app's own still-in-
-  // progress initial boot. Waiting for the home screen to actually be up first avoids that race.
-  await Spectra.get("~toggle-sidebar-btn").waitForElement(30000);
-
-  // No prior navigation, no button clicks — this jumps straight to the route via
-  // `adb shell am start`, exactly like opening the app from a push notification or an
-  // external link would.
-  await Spectra.navigate("testspectra-demo://deeplink-target");
-  await Spectra.get("~deeplink-target-marker").waitForElement(10000);
-
-  await Spectra.get("~deeplink-target-marker").shouldHaveText("deeplink-target");
-  await Spectra.get("~deeplink-received-message").shouldHaveText("(none)");
-
-  await Spectra.get("~back-to-home-btn").click();
-
-  // Deep links can carry query params — assert they survive the intent all the way to the screen.
-  await Spectra.navigate("testspectra-demo://deeplink-target?message=hello-from-deep-link");
-
-  await Spectra.get("~deeplink-received-message").waitForElement(10000);
-  await Spectra.get("~deeplink-received-message").shouldHaveText("hello-from-deep-link");
-
-  await Spectra.get("~back-to-home-btn").click();
-});
+it("Navigate directly to a native route via Spectra.navigate() and an Android deep link", async () => {
+  // The orchestrator's own bootstrap launches the app (fire-and-forget, ~1.5s wait) before any
+  // test code runs at all — other tests never notice because their first action is a click()
+  // with its own generous poll budget, which absorbs whatever's left of the cold start. This
+  // test's first action is Spectra.navigate() itself, which is also fire-and-forget and has no
+  // such budget, so without this it races the deep-link intent against the app's own still-in-
+  // progress initial boot. Waiting for the home screen to actually be up first avoids that race.
+  await Spectra.get("~toggle-sidebar-btn").waitForElement(30000);
+
+  // No prior navigation, no button clicks — this jumps straight to the route via
+  // `adb shell am start`, exactly like opening the app from a push notification or an
+  // external link would.
+  await Spectra.navigate("testspectra-demo://deeplink-target");
+  await Spectra.get("~deeplink-target-marker").waitForElement(10000);
+
+  await Spectra.get("~deeplink-target-marker").shouldHaveText("deeplink-target");
+  await Spectra.get("~deeplink-received-message").shouldHaveText("(none)");
+
+  await Spectra.get("~back-to-home-btn").click();
+
+  // Deep links can carry query params — assert they survive the intent all the way to the screen.
+  await Spectra.navigate("testspectra-demo://deeplink-target?message=hello-from-deep-link");
+
+  await Spectra.get("~deeplink-received-message").waitForElement(10000);
+  await Spectra.get("~deeplink-received-message").shouldHaveText("hello-from-deep-link");
+
+  await Spectra.get("~back-to-home-btn").click();
+});

package/templates/default/specs/DeepLink/TC-0018-navigate-via-deep-link/spec.md

@@ -1,29 +1,29 @@
----
-id: TC-0018-navigate-via-deep-link
-title: Navigate directly to a native route via Spectra.navigate() and an Android deep link
-priority: High
-caseType: Positive
-status: ready-for-automation
-coverage:
-  web: unsupported
-  mobile: automated
----
-
-# Navigate directly to a native route via Spectra.navigate() and an Android deep link
-
-On Android, `Spectra.navigate(uri)` runs `adb shell am start -a android.intent.action.VIEW -d
-<uri>` against the app's own registered scheme (`testspectra-demo://`, declared in
-`app.json`/`AndroidManifest.xml`) — jumping straight to a route without walking through the UI
-first, the same way a push notification or an external link would open the app in production.
-
-Web coverage is `unsupported`: on web, `Spectra.navigate()` already does the equivalent thing
-via a normal URL (see any other TC's `browser.url(...)`/`Spectra.navigate(...)` call) — there's no
-separate "deep link" concept to demonstrate there.
-
-## Test Steps
-1. Wait for the app home screen to finish booting
-2. Navigate via a deep link to the target route without query params
-3. Assert the target marker is shown and the received message is "(none)"
-4. Navigate via a deep link carrying a query-param message
-5. Assert the received message matches the deep-link param
-6. Return to the home screen
+---
+id: TC-0018-navigate-via-deep-link
+title: Navigate directly to a native route via Spectra.navigate() and an Android deep link
+priority: High
+caseType: Positive
+status: ready-for-automation
+coverage:
+  web: unsupported
+  mobile: automated
+---
+
+# Navigate directly to a native route via Spectra.navigate() and an Android deep link
+
+On Android, `Spectra.navigate(uri)` runs `adb shell am start -a android.intent.action.VIEW -d
+<uri>` against the app's own registered scheme (`testspectra-demo://`, declared in
+`app.json`/`AndroidManifest.xml`) — jumping straight to a route without walking through the UI
+first, the same way a push notification or an external link would open the app in production.
+
+Web coverage is `unsupported`: on web, `Spectra.navigate()` already does the equivalent thing
+via a normal URL (see any other TC's `browser.url(...)`/`Spectra.navigate(...)` call) — there's no
+separate "deep link" concept to demonstrate there.
+
+## Test Steps
+1. Wait for the app home screen to finish booting
+2. Navigate via a deep link to the target route without query params
+3. Assert the target marker is shown and the received message is "(none)"
+4. Navigate via a deep link carrying a query-param message
+5. Assert the received message matches the deep-link param
+6. Return to the home screen

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

@@ -1,9 +1,9 @@
----
-id: suite-deep-link
-name: DeepLink
-description: Navigating directly to a native route via Spectra.navigate() and an adb deep link
-executionOrder: 2.2
-parallel: true
----
-
-# Suite: DeepLink
+---
+id: suite-deep-link
+name: DeepLink
+description: Navigating directly to a native route via Spectra.navigate() and an adb deep link
+executionOrder: 2.2
+parallel: true
+---
+
+# Suite: DeepLink

package/templates/default/specs/ElementMatchers/TC-0003-visibility-and-dom/mobile.test.ts

@@ -1,11 +1,11 @@
-it("Verify element visibility and existence matchers", async () => {
-  await MatchersPage.open("visibility");
-
-  // Element visibility (positive and negative)
-  await MatchersPage.visibleElement.shouldBeVisible();
-  await MatchersPage.hiddenElement.shouldNotBeVisible();
-
-  // DOM existence (positive and negative)
-  await MatchersPage.existingElement.shouldExist();
-  await Spectra.get("~non-existent-element").shouldNotExist();
-});
+it("Verify element visibility and existence matchers", async () => {
+  await MatchersPage.open("visibility");
+
+  // Element visibility (positive and negative)
+  await MatchersPage.visibleElement.shouldBeVisible();
+  await MatchersPage.hiddenElement.shouldNotBeVisible();
+
+  // DOM existence (positive and negative)
+  await MatchersPage.existingElement.shouldExist();
+  await Spectra.get("~non-existent-element").shouldNotExist();
+});