Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

TESTING

Category: 11. Domain / Industry Hackathons
Section: Phase 3: Execution & Quality


13. TESTING.md

Purpose: To create a manual testing checklist including regulatory compliance testing.

Act as a QA engineer specializing in [INDUSTRY NAME] applications.
Using the PRD and Compliance Specification below, create a Testing document for an industry hackathon project.

PRD: [PASTE PRD]
COMPLIANCE_SPEC: [PASTE COMPLIANCE_SPEC]

Provide:
1. Testing strategy for industry applications
2. Functional testing (Core industry features)
3. Compliance testing (Does it meet regulations?)
4. Security testing (PII, PHI, Financial data)
5. Integration testing (Industry APIs)
6. Data validation testing
7. Edge cases (Industry-specific)
8. User acceptance testing checklist (With personas)
9. A manual testing checklist for the demo
10. How to document known compliance limitations for judges

Keep the testing plan simple enough for beginner developers to execute under time pressure.
Highlight compliance-critical test cases.