Skip to content

God-view date-browse test plan

Status: Manual regression checklist. The repository has Playwright infrastructure, but this specific date-browse journey is not currently represented in the browser specs.

Audience: QA, feature-flagged testers, and engineers converting the journey to automation.

Feature summary

The hidden Debug Solutions dialog (god-view, feature-flag-gated behind "DebugSolutions") now supports browsing solutions for other calendar dates when viewing a Daily puzzle, via "Previous day" and "Next day" buttons. This enables testers and admins to quickly review past and future daily puzzles' solutions without having to manually navigate the app.

The feature includes a spoiler deterrent: the first time a tester navigates to a different day's solutions within a single dialog session, a window.confirm() warning appears. Confirming this warning sets a server-side flag that excludes that date from the tester's personal stats and streaks (but does not affect group standings). This prevents unintended spoiler-browsing from inflating the admin's own score records. If the dialog is closed and reopened, the warning resets and appears again on the next navigation attempt.

Why manual, not automated

The repository now has Playwright and React Testing Library infrastructure, but this complete dialog/date-navigation journey is not automated. Backend endpoint and spoiler-exclusion behavior has focused tests; this checklist retains the browser-level interaction, loading, and confirmation scenarios that still require manual execution or a future Playwright spec.

Automation direction: Use this checklist as the basis for a focused Playwright journey. Keep the manual procedure until the browser spec covers the same scenarios and is part of the applicable validation gate.

Prerequisites

  • Feature flags enabled: The "DebugSolutions" feature flag must be active for your user. Verify in the hamburger menu (mobile) or dropdown (desktop); "Debug solutions" should appear under god-view tools.
  • God-view access: God-view is normally hidden from regular players. It is only visible if your user account is targeted by at least one of the feature flags: "PuzzleMetadata", "DebugSolutions", or "ResetDaily" (see doc/roadmap.md's feature flag targeting runbook).
  • Puzzle context: Tests should be run against the Letter Golf Daily puzzle (not practice). Practice puzzles have no date, so date-nav buttons do not appear.

Test scenarios

Scenario Steps Expected result
1. Date-nav buttons appear for daily, absent for practice (a) Open the hamburger menu / dropdown on the Letter Golf Daily page. (b) Click "Debug solutions". (c) Observe the dialog that opens. (d) Close the dialog. (e) Navigate to a practice puzzle (e.g., from the Play menu). (f) Open the hamburger menu and click "Debug solutions" again. (a–c) For the Daily puzzle, the "Previous day" and "Next day" buttons flanking the date (e.g., [Previous day] 2026-08-16 [Next day]) are visible and enabled. (e–f) For the practice puzzle, the date-nav buttons do not appear in the dialog. Only the puzzle key, seed word, and solutions list are shown.
2. First nav click within a dialog session shows the confirm() warning (a) Open "Debug solutions" on the Daily puzzle. (b) Click "Previous day". (c) Read the displayed window.confirm() dialog. (a) The dialog opens normally. (b) A browser confirmation dialog appears with the exact text: "Viewing another day's solutions before you've completed that day's Daily play will exclude it from your stats and streak (group standings aren't affected). Continue?" with OK and Cancel buttons.
3. Cancelling the confirm dialog leaves date unchanged Continuing from Scenario 2: (d) Click Cancel on the confirm dialog. (e) Observe the solutions dialog. (d–e) The confirm dialog closes. The displayed date, solutions list, and puzzle key remain at the original date (unchanged). The Previous/Next buttons remain visible and enabled. No API request for the other day occurs.
4. Confirming navigates to new date; subsequent nav clicks do NOT re-prompt Continuing from Scenario 2: (d) Click OK on the confirm dialog. (e) Wait for the loading state to complete. (f) Verify the displayed date has changed. (g) Click "Next day" again (or "Previous day"). (h) Verify no confirm dialog appears. (d–e) The API request for the previous day completes. The date display advances to the prior day and the solutions list updates. (f) The date has changed (e.g., from 2026-08-16 to 2026-08-15). (g) A second navigation click proceeds immediately without showing the confirm dialog again. (h) The solutions for the next date load and display (buttons remain disabled until loading finishes).
5. Reopening the dialog resets the "already warned" state Continuing from Scenario 4: (i) Click the X or backdrop to close the Debug solutions dialog. (j) Click "Debug solutions" again from the menu. (k) Click "Previous day" (or any navigation button). (i–j) The dialog closes and reopens. The date display resets to the current daily puzzle's date, and the solutions refresh. (k) The confirm dialog reappears, confirming the warning state was reset on dialog reopen.
6. Navigating past the pre-generation horizon shows 404 error (a) Open "Debug solutions" for today's Daily puzzle. (b) Click "Next day" multiple times in succession to navigate far into the future (e.g., 20+ days ahead). (c) Observe when the API reaches a date beyond the typical 14-day pre-generation window. (a–c) At some point, a click will trigger a loading state, then an inline error message: "That date's puzzle hasn't been generated yet." in red/error styling. The date display does not advance—it remains at the last valid date before the 404. The Previous/Next buttons re-enable, allowing navigation back to valid dates. Subsequent clicks can still navigate forward or backward from the last valid position.
7. Navigating to a very old past date shows solutions correctly (a) Open "Debug solutions" for today's Daily puzzle (assume today is 2026-08-16). (b) Click "Previous day" multiple times to navigate back to an old date, e.g., 2026-01-01 or 2025-08-01. (c) Wait for the solutions to load. (a–c) The solutions for the old date load and display normally. The puzzle key, seed word, and solutions list for that historical date appear in the dialog with no errors. Date-nav buttons remain functional for further navigation.
8. Previous/Next buttons disabled during loading, re-enabled after (a) Open "Debug solutions". (b) Confirm ("DebugSolutions" is gated and available). (c) Click "Previous day" once. (d) Immediately (before the API response returns) observe the button states. (e) Wait for the loading state to complete. (a–c) A loading request is triggered. (d) Both "Previous day" and "Next day" buttons have a disabled attribute (grayed out, not clickable). The center date display and "Loading…" message indicate the pending state. (e) Once the API response arrives, the buttons re-enable and the new date/solutions display.
9. Backend: verify stats exclusion for pre-completion browsing (a) As a test admin/tester, open "Debug solutions" for today's Daily puzzle via the god-view menu. (b) Click "Previous day" and confirm the warning. (c) Confirm navigating to yesterday's solutions. (d) Backend verification only (not UI-visible): Query the database or review server logs / the GetDebugSolutionsForDateEndpointTests.cs test suite to confirm that viewing yesterday's solutions before completing yesterday's play has set an exclusion flag on the tester's account for that date. (e) Verify that the exclusion removes that date's score from the player's personal stats and streak, but group standings for that date still include the player normally. (a–d) The dialog and navigation work as described in earlier scenarios. (d) Backend testing confirms the exclusion flag was written (see MiniGamesBackEnd.Tests/GetDebugSolutionsForDateEndpointTests.cs). (e) The player's personal stats/streak endpoints no longer count that date; however, group standings endpoints still reflect that the player exists and has group membership for that date.
10. Regression: existing daily-puzzle solutions behavior unchanged (a) Open "Debug solutions" on the Daily puzzle, assuming the tester has already completed today's play. (b) Verify the dialog displays the current day's puzzle key, seed word, and solutions. (c) Do not click Previous/Next. (d) Close the dialog and reopen it. (a–d) All existing behavior is unchanged: the dialog shows the current day's puzzle metadata and solutions normally. The date-nav buttons are present (as per Scenario 1), but this scenario confirms the core solutions-display functionality continues to work as before, only now with optional date navigation.

Out of scope

  • Feature-flag permission boundary testing: Verification that non-targeted users cannot access god-view or date-browse is assumed to be covered by existing feature-flag permission tests in the backend (see doc/roadmap.md).
  • Cosmos DB stats-exclusion verification: Direct database-level verification that the exclusion flag is correctly persisted and queried is the responsibility of the backend test suite, specifically MiniGamesBackEnd.Tests/GetDebugSolutionsForDateEndpointTests.cs. Frontend testing confirms the side effect (exclusion occurs and affects stats), but not the database state itself.
  • Load and performance testing: This plan does not cover stress testing, high-volume date-browsing, or performance benchmarks. Performance validation is deferred to dedicated load-testing runs (see doc/performance.md if applicable).
  • API contract versioning: Breaking changes to /v1/letter-golf/daily/{date}/debug-solutions or related endpoints are tracked separately in the API versioning strategy.