Test Guide: Card #spine-006
forge | dashboard-ui | main | 2026-04-08 21:12:04
What Was Built
Ralph completed: KFS harvest markers expanded (13 new patterns for Ralph output). KFS brain_events table now has data (was empty for weeks)
What This Unlocks
Verify the changes work as expected.
How To Verify
Follow each step. In the dashboard /verify tab, mark each as passed or failed, then submit your verdict.
Step 1. Open the dashboard page where the change was made — look for the new or updated feature
Expected: Page loads fully. The new feature is visible on screen — look for new tabs, panels, cards, or changed layout. No blank sections or loading spinners stuck.
Why: First check: can you SEE what was built? If the feature is not visible, everything else is moot.
Step 2. USE the new feature — click every button, toggle, link, and interactive element you can find. Try the happy path first.
Manual: Click through the feature. Try each button, dropdown, toggle. Fill any forms with sample data.
Expected: Every click does something logical. Buttons respond on hover/click. Dropdowns open and close. Forms accept input. No dead buttons or broken links. No console errors (open DevTools > Console to check).
Why: Proves the feature WORKS, not just renders. Dead buttons and broken flows are the most common issues.
Step 3. Check the visual quality — is text readable? Cards aligned? Colors correct for dark theme? Nothing overlapping or cut off?
Manual: Scan the page slowly. Look at headings, body text, card edges, spacing between elements.
Expected: Clean layout with consistent spacing. Text is legible (not too small, not truncated). Dark theme colors look intentional — no white boxes or invisible text. Cards and panels have even margins.
Why: Catches visual regressions that automated tests miss — layout issues, color problems, text overflow.
Step 4. Test the user flow end-to-end — does the journey from A to B to C make sense? Are there dead ends?
Manual: Start from the navigation entry point. Click into the feature, do something, then try to go back or move to the next logical action.
Expected: Navigation feels natural. You can get into the feature AND back out. Actions have visible feedback (success messages, state changes). No confusing dead ends where you do not know what to do next.
Why: UX flow check — even if individual elements work, the overall journey needs to be logical and intuitive.
Step 5. Test edge cases — resize browser to phone width (~375px), try with empty data if possible, look for overflow with long text
Manual: Resize browser to 375px width. Also try expanding any text-heavy sections.
Expected: Content stacks vertically on mobile. No horizontal scrolling. Buttons are tap-sized. Long text wraps cleanly without breaking layout. Empty states show a helpful message, not a blank void.
Why: Edge cases reveal fragile UI — mobile users and unusual data are where things break most often.
Step 6. Verify the backend API is feeding data to what you see
curl -sf http://localhost:3002/health | python3 -m json.tool
Expected: JSON with status: ok. If this fails, the dashboard may be showing stale or missing data.
Why: Backend check comes last — now that you know what the UI looks like, confirm the data pipeline is healthy.
QA Gate Results
No QA gate log found.
Diff Summary
No diff available