UAT: US Household (PR #556)

[SakshiKekre]

Parent issue: #557 (see setup instructions there)

Test the Report Builder flow for US with Household populations.

Test scenarios

Test each scenario using both Card view and Row view:

• Create a report with a new household population
• Create a report using an existing/saved household
• Build a household with multiple people
• Assign variables to specific entities (tax units, SPM units)
• Select/create a policy and add to simulation
• Complete full report creation flow
• Verify simulation canvas updates correctly

View mode comparison

After testing both views, provide feedback:

• Which view (Card or Row) felt more intuitive?
• Any issues specific to one view?
• Preference and why?

Questions to answer

• Is household creation intuitive within the flow?
• Are entity assignments (tax units, SPM units) clear?
• Any bugs, glitches, or confusing UI elements?

[AnushkaNilangekar]

UAT Findings:

Overall Impression

• The redesigned Report Builder feels very polished and intuitive.
• Household creation is smooth with no confusion.
• Card view provides a clear, high-level understanding of the workflow.
• Excellent attention to detail: icons, rename report, collapsible sections, and informative popups.

Issues & Observations

1. Indicator Visibility (Top Right)

• Workflow step: Report Builder overview
• View mode: Both (more noticeable in Card)
• Expected: Indicators should be immediately recognizable
• Actual: The two circular indicators in the top-right are small; one is blinking but hard to notice without zooming
• Severity: Minor
• Suggestion: Slightly increase size or change color to be darker

2. Card View Readability (Font Size & Spacing)

• Workflow step: General navigation in Report Builder
• View mode: Card
• Expected: Content should be readable without zooming
• Actual: Some text feels small
• Severity: Minor
• Suggestion: Increase font size slightly and expand cards into available whitespace

3. Missing Closing Bracket in Variable Label

• Workflow step: Adding variables
• View mode: Both
• Expected: Correct variable label formatting
• Actual: “Federal tax income (reported” is missing a closing bracket
• Severity: Minor (UI text bug)

4. Variable Units & Context

• Workflow step: Variable selection
• View mode: Both
• Expected: Clear understanding of variable meaning and units
• Actual: Some variables (e.g., battery capacity, energy savings) lack visible units after adding to the household
• Severity: Minor / Enhancement
• Suggestions:
  • Display units where applicable
  • Add an info ("i") icon that shows the same description text (that is currently displayed during variable selection) next to the variable on hover after it is added to the household

5. Childcare Variables Applied to All Individuals

• Workflow step: Assigning household variables
• View mode: Both
• Expected: Individual-specific variables should apply logically
• Actual: Adding childcare-related variables applies to all individuals
• Severity: Very Minor
• Question: Should these default to dependents only?

6. Policy Creation Validation UX

• Workflow step: Creating a new policy
• View mode: Both
• Expected: Clear indication of missing required fields
• Actual: Create Policy button is disabled when policy name is missing (correct behavior), but missing fields are not visually highlighted when 'Submit' is clicked
• Severity: Minor
• Suggestion: Highlight required fields when user attempts to submit

7. Navigation Error After Report Creation

• Workflow step: After creating a new report and navigating back to Report Builder
• View mode: Both
• Expected: Smooth navigation back to Report Builder
• Actual: Encountered an error when returning to Report Builder
• Severity: Major
• Evidence: Loom recording: https://www.loom.com/share/c1e5a44cc4444a9ba9dab4b22d01f63e

8. Unexpected Application Errors (Non-Deterministic)

• Workflow step: Switching between Reports tab, individual reports, and Report Builder
• View mode: Both
• Expected: Stable navigation
• Actual: “Unexpected application error” appeared intermittently; not consistently reproducible
• Severity: Major
• Notes:
  • Occurred after navigating back and forth between reports and builder
  • Happened multiple times but not with a clear trigger
  • Screenshot:

(There was also another one that said "Cannot read properties of undefined (reading 'people')")

9. Simulation Failures for Specific Configurations

• Workflow step: Create report using existing household
• View mode: Row
• Scenario & Outcome:
  Existing household + current law → Society-wide calculation failed
  Existing household + no reform → Worked for 2026
  Existing household + reform → Worked for 2025
  Other year/policy combinations eventually worked
• Severity: Major
• Note: Error appears configuration-dependent

Positive UX Highlights

• Household creation flow is very intuitive
• Adding/removing variables is smooth
• Popups are informative and helpful

View Mode Comparison

1. Which view felt more intuitive?
   Card View
2. Issues specific to one view

• Row View:
  • Extends beyond screen height
  • Requires frequent vertical scrolling
• Card View:
  • More compact and easier to scan
  • Would benefit from slightly larger fonts

3. Overall Preference
   Card View
   Reason: Clearer mental model of progress and components, less scrolling, better high-level visibility

[AnushkaNilangekar]

Based on these observations, I can create sub-issues for the ones that have severity: major if you would like me to!