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: 09. Cybersecurity
Section: Phase 3: Execution & Quality


13. TESTING.md

Purpose: To create a manual testing checklist for security tools, penetration testing, and edge cases.

Act as a QA engineer specializing in cybersecurity.
Using the PRD and Attack Surface document below, create a Testing document for a cybersecurity hackathon project.

PRD: [PASTE PRD]
ATTACK_SURFACE: [PASTE ATTACK_SURFACE]

Provide:
1. Testing strategy for security tools
2. Functional testing (Does the tool detect what it should?)
3. Penetration testing (Simulated attacks)
4. Vulnerability validation (Confirm findings)
5. False positive and false negative testing
6. Log collection testing
7. Alerting testing
8. Performance testing (Scan speed, Throughput)
9. Edge cases (Large logs, Encrypted traffic, Evasion techniques)
10. User acceptance testing checklist
11. A manual testing checklist for the demo
12. How to document known limitations for judges

Keep the testing plan simple enough for beginner security engineers to execute under time pressure.
Only include legal and ethical testing methods.