TESTING
Category: 13. Social Impact / Civic
Section: Phase 3: Execution & Quality
13. TESTING.md
Purpose: To create a manual testing checklist including accessibility testing and community validation.
Act as a QA engineer specializing in social impact applications.
Using the PRD and Accessibility Spec below, create a Testing document for a social impact hackathon project.
PRD: [PASTE PRD]
ACCESSIBILITY_SPEC: [PASTE ACCESSIBILITY_SPEC]
Provide:
1. Testing strategy for social impact applications
2. Functional testing (Core features)
3. Accessibility testing (Screen readers, Keyboard, Contrast)
4. Low-bandwidth testing (Slow network, Offline)
5. Low-end device testing
6. Multilingual testing
7. Integration testing (Government/NGO APIs)
8. Edge cases (Missing data, Vulnerable user scenarios)
9. Community validation (Testing with real users or proxies)
10. A manual testing checklist for the demo
11. How to document known limitations for judges
Keep the testing plan simple enough for beginner developers to execute under time pressure.
Prioritize accessibility and inclusion in all tests.