freshyo/docs/test-cases/fallback-legacy-pages.md
2026-10-18 18:19:15 +05:30

27 lines
3 KiB
Markdown

# Fallback and legacy standalone pages — conditional
Scope inventory: fallback login, user-home/user-details/order-details, location-marker, user-connect, create-coupon, vendor-order-list, super-admin, inauguration, home/demo. Presence of a route does not imply supported release functionality. Validate active ownership with product/operations; unsupported/demo pages are N/A with reason, not PASS.
> **STATUS: EXCLUDED from the automated run (2026-10-18).**
> The fallback/legacy standalone app (`apps/fallback-ui`) is **out of scope for this release cycle** (low priority —
> owner instruction). This surface is not started, and its cases are reported as `SKIPPED` rather than
> `PASS`/`FAIL`/`NOT RUN`. The cases below are **retained unchanged** (nothing removed).
| ID | Priority | Action / input | Expected result |
|---|---|---|---|
| LEGACY-01 | P1 | Approved fallback login and direct allowed destination. | Correct session/role/context; no undocumented bypass of primary apps. |
| LEGACY-02 | P0 | Anonymous/customer visits operational user/order/super-admin routes. | Private reads/mutations still require intended authority. |
| LEGACY-03 | P0 | User/order detail with guessed foreign IDs. | Ownership/region denial; URL knowledge not authorization. |
| LEGACY-04 | P1 | Supported location marker saves intended order/address coords. | Correct target only; region/bound not silently overwritten. |
| LEGACY-05 | P1 | Missing/malformed marker params/coords and permission denied. | Recoverable validation; no arbitrary write or endless map. |
| LEGACY-06 | P0 | Standalone coupon creation from staff A vs customer/B/global attempt. | Same current regional/global authoring restrictions as primary router. |
| LEGACY-07 | P1 | User-connect flow with approved identity/link. | No cross-account join/impersonation; link policy explicit. |
| LEGACY-08 | P1 | Vendor page expired/permanent/missing snippet. | Conditional vendor authority enforced; useful empty/error state. |
| LEGACY-09 | P2 | Inauguration/demo promotional page. | No production mutation, secret exposure or broken supported navigation. |
| LEGACY-10 | P1 | Browser refresh/back/cold direct route. | No stale local auth assumption; correct guarded page. |
| LEGACY-11 | P1 | Active backend endpoint changed since legacy UI shipped. | Current request schema (boundId/couponIds/skuId) respected; no `as any`-hidden mismatch. |
| LEGACY-12 | P0 | API environment/base URL in standalone deployment. | Approved host; no unintended dev data or production mutation from staging. |
| LEGACY-13 | P1 | Network/asset error, corrupt local state. | Recoverable safe behavior; no false order/compensation success. |
| LEGACY-14 | P2 | Mobile browser keyboard/safe-area/maps and desktop layout. | Supported active pages remain usable and accessible. |
See [vendor](vendor-snippets.md), [security](authorization-api-contracts.md), [configuration](constants-configuration.md). Require a support decision per route before including legacy pages in a release gate.