PolicyEngine / PolicyEngine/policyengine-app-v2

UAT: Report Builder Redesign Testing and fixing (PR #556)

Open
#557 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
1
Forks
3
Avg merge
1d 50m
Merged PRs (30d)
39

Description

Context

We're redesigning the report builder experience with modal-based workflows for selecting and creating policies, populations, and households. Before merging #556, we need thorough user acceptance testing.

Setup

git fetch origin
git checkout feat/report-setup-reflow
npm install
npm run dev

This starts two dev servers:

  • Website: http://localhost:3000
  • Calculator: http://localhost:3001

Cross-app links (logo, "Enter PolicyEngine" button) should correctly navigate between these local servers.

Goal

  1. Familiarize yourself with the new Report Builder design
  2. Test both Card view and Row view display modes
  3. Identify bugs, UX issues, and pain points
  4. Provide feedback on which view mode you prefer

Pre-work (everyone, ~15 min)

Spend 15 minutes on app.policyengine.org exploring the current report creation flow. This gives you baseline context for comparison.


Assignments

Each person tests the full Report Builder flow for their country + scope, using both Card and Row views:

  • US National + Subnational - #559
  • US Household - #560
  • UK National + Subnational - #561
  • UK Household - #562

How to Report Findings

For each issue found, include:

  1. Workflow step where issue occurred
  2. View mode (Card/Row/Both)
  3. Expected behavior vs Actual behavior
  4. Screenshot or screen recording if possible
  5. Severity: Blocker / Major / Minor / Enhancement

Comment directly on #556 or create issues with label uat-556.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Check out feat/report-setup-reflow, run npm install and npm run dev, then compare the local Report Builder at ports 3000 and 3001 with app.policyengine.org. Test the assigned country and scope in both Card and Row views, recording workflow step, expected versus actual behavior, severity, and evidence. Done means the assigned flows have been tested and findings are reported on #556 or as uat-556 issues.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
frontend, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.