psa-systems/mokosh-apps
Watch
9
0
Fork
You've already forked mokosh-apps
 0
Code Issues Pull requests 1 Projects Releases 14 Packages Wiki Activity Actions

docs(qa): add technique-rich field and button audit prompt #225

Merged
nrupard merged 2 commits from docs/MAPPS-221-qa-field-button-audit-prompt into main 2026-06-16 16:58:52 +02:00
Conversation 0 Commits 2 Files changed 2 +138
David commented 2026-06-16 16:33:01 +02:00
Owner
Copy link

Prior QA passes were asked to be "thorough" but still left real UI defects (MAPPS-210..220, PMS-372..374) because the existing prompts describe WHAT to cover, not the concrete TECHNIQUES that expose the bugs. Agents kept eyeballing forms and submitting happy-path values.

Add dev-docs/qa-field-and-button-audit-prompt.md: a single reusable agent prompt that mandates, per field and per button on every screen, the exact methods that found the latest batch. Per field: programmatic enumeration of HTML constraint attributes (maxlength/min/max/step/pattern), the validity.stepMismatch/rangeOverflow/rangeUnderflow probe (catches money fields that reject cents and accept negatives without submitting), sequential fix-the-first-error-to-expose-the-next testing, format-field probes (email/url-scheme/phone-E.164/country-ISO/timezone-IANA/slug/RRULE/date-range), error-display quality checks (field highlighted and named vs generic banner), and post-create persistence verification via API (the technique that caught the negative payment, raw slug, and garbage RRULE). Adds an explicit BUTTON audit (disabled-but-styled-enabled, dead pointer-cursor controls, mis-routed/404 create routes) and the browser/WASM gotchas (fetch interceptor unreliable, navigation wipes globals, unsaved-changes guard needs double navigation, no top-level await).

#MAPPS-221

Prior QA passes were asked to be "thorough" but still left real UI defects (MAPPS-210..220, PMS-372..374) because the existing prompts describe WHAT to cover, not the concrete TECHNIQUES that expose the bugs. Agents kept eyeballing forms and submitting happy-path values. Add dev-docs/qa-field-and-button-audit-prompt.md: a single reusable agent prompt that mandates, per field and per button on every screen, the exact methods that found the latest batch. Per field: programmatic enumeration of HTML constraint attributes (maxlength/min/max/step/pattern), the validity.stepMismatch/rangeOverflow/rangeUnderflow probe (catches money fields that reject cents and accept negatives without submitting), sequential fix-the-first-error-to-expose-the-next testing, format-field probes (email/url-scheme/phone-E.164/country-ISO/timezone-IANA/slug/RRULE/date-range), error-display quality checks (field highlighted and named vs generic banner), and post-create persistence verification via API (the technique that caught the negative payment, raw slug, and garbage RRULE). Adds an explicit BUTTON audit (disabled-but-styled-enabled, dead pointer-cursor controls, mis-routed/404 create routes) and the browser/WASM gotchas (fetch interceptor unreliable, navigation wipes globals, unsaved-changes guard needs double navigation, no top-level await). #MAPPS-221
docs(qa): add technique-rich field and button audit prompt
All checks were successful
Check / clippy + fmt + tests (pull_request) Successful in 57s
Details
3adffec167 
Prior QA passes were asked to be "thorough" but still left real UI defects (MAPPS-210..220, PMS-372..374) because the existing prompts describe WHAT to cover, not the concrete TECHNIQUES that expose the bugs. Agents kept eyeballing forms and submitting happy-path values.

Add dev-docs/qa-field-and-button-audit-prompt.md: a single reusable agent prompt that mandates, per field and per button on every screen, the exact methods that found the latest batch. Per field: programmatic enumeration of HTML constraint attributes (maxlength/min/max/step/pattern), the validity.stepMismatch/rangeOverflow/rangeUnderflow probe (catches money fields that reject cents and accept negatives without submitting), sequential fix-the-first-error-to-expose-the-next testing, format-field probes (email/url-scheme/phone-E.164/country-ISO/timezone-IANA/slug/RRULE/date-range), error-display quality checks (field highlighted and named vs generic banner), and post-create persistence verification via API (the technique that caught the negative payment, raw slug, and garbage RRULE). Adds an explicit BUTTON audit (disabled-but-styled-enabled, dead pointer-cursor controls, mis-routed/404 create routes) and the browser/WASM gotchas (fetch interceptor unreliable, navigation wipes globals, unsaved-changes guard needs double navigation, no top-level await).

#MAPPS-221
docs(qa): index the three QA prompts in the dev-docs README
All checks were successful
Check / clippy + fmt + tests (pull_request) Successful in 1m5s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
52014ef3f5 
The QA prompt docs (test plan, input-validation matrix, and the new field-and-button audit) were not listed in the dev-docs README contents table. Add all three so the QA technique layer is discoverable alongside the rest of the developer docs.

#MAPPS-221
nrupard deleted branch docs/MAPPS-221-qa-field-button-audit-prompt 2026-06-16 16:58:52 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/mokosh-apps!225
No description provided.