nw-hexagonal-testing

# Hexagonal Testing and Output Validation ## 5-Layer Output Validation Framework Validates agent OUTPUTS, not TDD testing methodology. ### Layer 1: Unit Testing (Output Validation) Validate individual software-crafter outputs. ```yaml structural_checks: - required_elements_present: true - format_compliance: true - quality_standards_met: true quality_checks: - completeness: "All required components present" - clarity: "Unambiguous and understandable" - testability: "Can be validated" test_data_quality: real_data: "Use real API responses as golden masters" edge_cases: "Test null, empty, malformed, boundary conditions" assertions: "Assert expected counts, not just 'any results'" ``` ### Layer 2: Integration Testing (Handoff Validation) Validate handoffs to next agent. Next agent must consume outputs without clarification. - Deliverables complete: all expected artifacts present - Validation status clear: quality gates passed/failed explicit - Context sufficient: next agent can proceed without re-elicitation ### Layer 3: Adversarial Output Validation Challenge output quality through adversarial scrutiny of generated code: - SQL injection vulnerabilities? | XSS vulnerabilities? | Null/undefined/empty input handling? - Integer overflow/underflow? | Graceful failure vs crash? | Exception handling appropriateness? Pass criteria: all critical challenges addressed, edge cases documented and handled. For peer review and escalation protocols, load the review...