functional-validation

Functional validation replaces mock-based testing by building and launching the real system with real dependencies, exercising it through actual user interfaces, and capturing evidence to produce evidence-backed verdicts.

Capture evidence during e2e testing by exercising the real system and saving all outputs to the e2e-evidence/ directory, then writing PASS/FAIL verdicts that directly quote specific evidence files to substantiate the functional validation results.

Yes, functional validation supports iOS, web, API, CLI, and full-stack scenarios. It uses platform detection to identify the project type and automatically selects the correct validation approach for building and exercising the specific real system.

The best way to replace mock-based testing is using a 4-step validation protocol: build and launch the real system with real dependencies, exercise it as a user would, capture evidence into e2e-evidence/, and write verdicts citing quoted evidence.

E2e validation lacks proof when relying on mocks instead of the live app. Functional validation ensures features work by building the real system with real dependencies, exercising it through real user interfaces, and documenting evidence-backed verdicts.