Objective
Audit the entire AgencyZero app so every actionable button/control is accounted for by either a real native automated outcome or an explicit manual-human test case. The report must not equate node presence, clicks dispatched, or jsdom coverage with working behavior.
Automated coverage requirement
For every safe headless action, add or strengthen ps-qa coverage against the QA profile for the actual user-visible outcome: opening/closing, changed selection/value, committed state, rendered content, disabled state, or other falsifiable result. Cover drift between component inventory, mounted QA fixtures, and application consumers.
Explicit manual-only exclusions from owner
- File dialogs that cannot be closed headlessly.
- Restarting the app.
- Starting/stopping the proxy.
- Actions that spend money, including starting a prompt.
These must still appear in the inventory with a manual test procedure and reason; they are excluded from automation, not omitted from coverage accounting.
Ambiguity rule
Do not invent additional exclusions. If an action is destructive, externally mutating, costly, or otherwise questionable and does not clearly fit the listed categories, ask the owner before classifying it.
Deliverables
- Generated or mechanically checked inventory of every app button/actionable control.
- Automated native outcome id for each safe control.
- Manual-test id, procedure, and exclusion reason for every approved exception.
- CI drift gate: new actionable controls cannot land unaccounted.
- Summary totals for automated, manual-only, and unaccounted; unaccounted must be zero.
- Full focused QA sweep completing in the established 1–2 minute budget where practical.
Objective
Audit the entire AgencyZero app so every actionable button/control is accounted for by either a real native automated outcome or an explicit manual-human test case. The report must not equate node presence, clicks dispatched, or jsdom coverage with working behavior.
Automated coverage requirement
For every safe headless action, add or strengthen ps-qa coverage against the QA profile for the actual user-visible outcome: opening/closing, changed selection/value, committed state, rendered content, disabled state, or other falsifiable result. Cover drift between component inventory, mounted QA fixtures, and application consumers.
Explicit manual-only exclusions from owner
These must still appear in the inventory with a manual test procedure and reason; they are excluded from automation, not omitted from coverage accounting.
Ambiguity rule
Do not invent additional exclusions. If an action is destructive, externally mutating, costly, or otherwise questionable and does not clearly fit the listed categories, ask the owner before classifying it.
Deliverables