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 reusable QA prompts for E2E testing and input validation #195

Merged
David merged 2 commits from docs/mapps-209-qa-prompts into main 2026-06-16 14:09:40 +02:00
Conversation 0 Commits 2 Files changed 2 +131
David commented 2026-06-16 10:28:00 +02:00
Owner
Copy link

Background

QA testing of the Mokosh PSA app is driven by reusable AI-agent prompts. This PR puts two of them under version control in dev-docs/.

What's added

  • dev-docs/qa-test-plan.md - broad end-to-end QA plan: recon, realistic related data seeding, per-screen Element Checklist, full CRUD lifecycle, input validation/fuzz, and cross-cutting auth/multi-tenancy checks. Written after a prior pass took shortcuts (treated "renders" as "tested", skipped Update/Delete, missed relationship features).
  • dev-docs/qa-input-validation-prompt.md - single-purpose, no-shortcuts per-field validation prompt. Makes every input field a tracked unit of work: build a Field Inventory across every form on every screen, classify each field by type, run a per-type validation matrix at BOTH the UI and API layer, and produce a Field Coverage Ledger. Added because input validation was under-tested when buried as one phase of the broad plan.

Notes

Docs only. No application code changes.

#MAPPS-209

## Background QA testing of the Mokosh PSA app is driven by reusable AI-agent prompts. This PR puts two of them under version control in `dev-docs/`. ## What's added - `dev-docs/qa-test-plan.md` - broad end-to-end QA plan: recon, realistic related data seeding, per-screen Element Checklist, full CRUD lifecycle, input validation/fuzz, and cross-cutting auth/multi-tenancy checks. Written after a prior pass took shortcuts (treated "renders" as "tested", skipped Update/Delete, missed relationship features). - `dev-docs/qa-input-validation-prompt.md` - single-purpose, no-shortcuts per-field validation prompt. Makes every input field a tracked unit of work: build a Field Inventory across every form on every screen, classify each field by type, run a per-type validation matrix at BOTH the UI and API layer, and produce a Field Coverage Ledger. Added because input validation was under-tested when buried as one phase of the broad plan. ## Notes Docs only. No application code changes. #MAPPS-209
docs(qa): add reusable QA prompts for E2E testing and input validation
All checks were successful
Check / clippy + fmt + tests (pull_request) Successful in 1m0s
Details
8957ba0218 
Add two AI-agent QA prompts under dev-docs: qa-test-plan.md (broad end-to-end plan with per-screen Element Checklist, realistic related seeding, CRUD lifecycle, and cross-cutting checks) and qa-input-validation-prompt.md (single-purpose, no-shortcuts per-field validation that builds a Field Inventory, runs a per-type matrix at both UI and API layers, and produces a Field Coverage Ledger).

#MAPPS-209
Merge branch 'main' into docs/mapps-209-qa-prompts
All checks were successful
Create release / Create release from merged PR (pull_request) Has been skipped
Details
Check / clippy + fmt + tests (pull_request) Successful in 1m0s
Details
2687bb37a7
David merged commit f1df2058d8 into main 2026-06-16 14:09:40 +02:00
David deleted branch docs/mapps-209-qa-prompts 2026-06-16 14:09:40 +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
1 participant
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!195
No description provided.