Spike: Validate parent login flow end-to-end #150

New issue

Open

opened 2026-03-28 19:57:53 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-28 19:57:53 +00:00

Owner

Type

Spike

Lineage

Standalone — emerged from session preparing for player email communications. Must validate login works before sending any emails to parents.

Repo

Multiple — forgejo_admin/westside-landing, forgejo_admin/basketball-api, Keycloak realm westside-basketball

Question

Does the complete parent login flow work end-to-end — from landing page sign-in through Keycloak auth to viewing their player profile and updating incomplete fields?

What to Explore

Landing to Sign In — verify Keycloak login page loads
Keycloak Auth — test with known parent email from DB
Post-Login Redirect — verify parent lands on dashboard not landing page
Player Linkage — verify email-based matching (Parent.email == Keycloak JWT email) works
Profile View — parent can see team assignment and player details
Profile Update — test updating missing fields for incomplete player
Forgot Password — test self-service reset flow
Mobile — test on 390px viewport

Tools: Chrome DevTools MCP and Playwright MCP for dual browser validation.
DB queries: kubectl exec into basketball-api pod to identify test parent accounts.

Success Criteria

Login flow documented as working or broken with specific failure points
Each step gets PASS/FAIL with evidence (screenshots, console errors, network traces)
Discovered bugs filed as separate Forgejo issues with backlog board items
Parent to player email linkage verified
Forgot password flow verified

Time-box

Maximum: 1 session. If blocked by Keycloak config, document findings and escalate.

project-westside-basketball
forgejo_admin/basketball-api #217 — bulk visibility depends on confirming parent flow works

### Type Spike ### Lineage Standalone — emerged from session preparing for player email communications. Must validate login works before sending any emails to parents. ### Repo Multiple — `forgejo_admin/westside-landing`, `forgejo_admin/basketball-api`, Keycloak realm `westside-basketball` ### Question Does the complete parent login flow work end-to-end — from landing page sign-in through Keycloak auth to viewing their player profile and updating incomplete fields? ### What to Explore 1. Landing to Sign In — verify Keycloak login page loads 2. Keycloak Auth — test with known parent email from DB 3. Post-Login Redirect — verify parent lands on dashboard not landing page 4. Player Linkage — verify email-based matching (Parent.email == Keycloak JWT email) works 5. Profile View — parent can see team assignment and player details 6. Profile Update — test updating missing fields for incomplete player 7. Forgot Password — test self-service reset flow 8. Mobile — test on 390px viewport Tools: Chrome DevTools MCP and Playwright MCP for dual browser validation. DB queries: kubectl exec into basketball-api pod to identify test parent accounts. ### Success Criteria - [ ] Login flow documented as working or broken with specific failure points - [ ] Each step gets PASS/FAIL with evidence (screenshots, console errors, network traces) - [ ] Discovered bugs filed as separate Forgejo issues with backlog board items - [ ] Parent to player email linkage verified - [ ] Forgot password flow verified ### Time-box Maximum: 1 session. If blocked by Keycloak config, document findings and escalate. ### Related - `project-westside-basketball` - `forgejo_admin/basketball-api #217` — bulk visibility depends on confirming parent flow works