Launch blocker: retest notepad, announcements, and customer messaging surfaces #8

Open
opened 2026-05-02 23:38:28 +00:00 by jester · 0 comments
Owner

Launch blocker

Retest the Portal/customer messaging surfaces before launch.

Context

Manual testing showed notepad / announcements / related messaging surfaces working previously, but they have not been revisited after the more recent Portal/API changes.

Scope to validate

  • Notepad / notes surface still loads and saves correctly.
  • Announcements surface still loads, displays, and updates correctly.
  • Any related customer-facing messaging/admin-managed content still works after current auth/API/Portal changes.
  • Permissions are correct: normal users should not reach admin-only creation/editing surfaces unless intentionally exposed.
  • Empty states, loading states, and error states are sane.
  • Mobile layout is acceptable enough for launch.

Validation needed

  • Manual test in current production-like environment.
  • Confirm API routes still match Portal usage.
  • Confirm persistence survives reload/logout/login.
  • Confirm no stale mock/manual-only assumptions remain.

Launch expectation

This does not require new feature work unless testing reveals regressions. It is a return-to-verify launch pass.

## Launch blocker Retest the Portal/customer messaging surfaces before launch. ## Context Manual testing showed notepad / announcements / related messaging surfaces working previously, but they have not been revisited after the more recent Portal/API changes. ## Scope to validate - Notepad / notes surface still loads and saves correctly. - Announcements surface still loads, displays, and updates correctly. - Any related customer-facing messaging/admin-managed content still works after current auth/API/Portal changes. - Permissions are correct: normal users should not reach admin-only creation/editing surfaces unless intentionally exposed. - Empty states, loading states, and error states are sane. - Mobile layout is acceptable enough for launch. ## Validation needed - Manual test in current production-like environment. - Confirm API routes still match Portal usage. - Confirm persistence survives reload/logout/login. - Confirm no stale mock/manual-only assumptions remain. ## Launch expectation This does not require new feature work unless testing reveals regressions. It is a return-to-verify launch pass.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jester/zlh-grind#8
No description provided.