@stardeck-customer-apps/testing 0.6.1 → 0.6.2

package/SKILL.md

@@ -246,6 +246,44 @@ cursor, limit })`; `list()` intentionally keeps its previous array shape.
   pairing pickers via `app.edge.seedDevices()` / `seedPeripherals()`.
 - `next/headers` (`headers()`/`cookies()`) inside handlers under `callRoute`.
 
+## End-to-end (Playwright) suite
+
+This package covers the hermetic in-process suite. The app ALSO has a separate
+Playwright e2e suite: specs in `e2e/*.spec.ts`, run with `npm run test:e2e`
+against the live dev server. It is NOT hermetic — real routes, real database,
+the sandbox's mock admin session.
+
+**When to use which**
+
+- Business logic, route handlers, edge cases, error paths → this package (fast,
+  isolated, deterministic).
+- Whole user journeys through the real UI (the flows a customer walks) → one
+  e2e spec per critical workflow.
+
+**Which flows get an e2e spec** (full guidance: `e2e/README.md`)
+
+One spec per critical workflow — "if this broke overnight, would the owner
+lose money or trust?" The flow types worth a journey: core transactions
+(cart → checkout → confirmation), creation → visibility (post a review →
+see it on the page), state transitions (order placed → fulfilled → status
+updates), cross-surface handoffs (storefront order → admin order list). NOT
+worth one: render-existence checks, admin CRUD minutiae, static pages,
+per-field validation (unit-test the route), login/logout (platform-provided).
+
+**E2e rules** (mirror `e2e/README.md`)
+
+- Whole journeys only: start at the flow's real entry page, end by asserting
+  the durable user-visible outcome — never render-existence checks ("button
+  renders", "page loads"). One happy path per workflow first; error plumbing
+  stays in this package's suite.
+- Group with `test.describe("workflow:<Name>")` using the same names as your
+  `describeWorkflow` blocks where they overlap.
+- Specs create uniquely-named data INSIDE the test body (retries re-run it)
+  and clean up after themselves.
+- Flake killers: user-facing locators (`getByRole`/`getByLabel`) over CSS,
+  never `waitForTimeout` (web-first assertions auto-wait), every test
+  independent of other tests' data and ordering.
+
 ## Rules
 
 - Test **business logic and route handlers**, not framework plumbing. Focus on

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stardeck-customer-apps/testing",
-  "version": "0.6.1",
+  "version": "0.6.2",
   "description": "Vitest test harness for Stardeck customer apps — in-process Postgres (PGlite) plus a control-plane simulator so the real Stardeck SDKs run unmodified in tests",
   "main": "dist/index.js",
   "module": "dist/index.mjs",