Add 64 integration and coverage tests for ValidationPipeline

[Copilot]

The PeasyAI ValidationPipeline lacked tests for its public API, cross-stage integration, error recovery, and several validator-specific behaviors, leaving core functionality implicitly trusted rather than verified.

New test file: tests/test_pipeline_and_integration.py

End-to-end pipeline flow (TestPipelineIntegration)

• Stage 1 (post-processor) fixes propagate correctly into Stage 2 (validators) — e.g., var x: int = 0; fixed before InlineInitValidator runs
• original_code is never mutated; fixes_applied and validators_run are populated correctly

Pipeline customisation (TestPipelineCustomisation)

• add_validator / remove_validator mechanics
• apply_fixes=False — issues still reported, code unchanged, fixes_applied empty
• include_test_validators=True adds TestFileValidator; custom constructor validator list works

PipelineResult public API (TestPipelineResultAPI)

• errors / warnings property filtering by severity
• to_review_dict() backward-compat shape (INFO issues surface in "warnings" key)
• summary() field presence

Convenience helpers (TestValidatePCodeConvenience)

• validate_p_code() and create_default_pipeline() round-trip
• is_test_file=True full flow: post-processor generates test declarations; separate apply_fixes=False path exercises TestFileValidator directly

Validator-specific gaps

• SyntaxValidator: }; detection, auto_fixable flag, fix correctness, occurrence count in message
• MachineStructureValidator: goto to undefined state (ERROR), self-loop goto (valid), empty state body (INFO), multi-machine independence

Input validation (TestInputValidationResult, TestDesignDocValidatorEdgeCases)

• InputValidationResult.success() / .failure() factories
• DesignDocValidator: exact MIN_LENGTH, exceeding MAX_LENGTH, all required sections present suppresses section warnings, extract_metadata edge cases

Error recovery (TestPipelineErrorHandling)

• Crashing validator does not propagate; recorded as INFO issue; subsequent validators still execute

File/project helpers (TestValidateFileAndProject)

• validate_file() reads from disk; PTst path triggers test-file mode in post-processor
• validate_project() validates all .p files; cross-file context enables DuplicateDeclarationValidator

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• huggingface.co
  • Triggering command: /tmp/peasyai_venv/bin/pytest /tmp/peasyai_venv/bin/pytest tests/ -v --ignore=tests/pipeline --tb=short -q (dns block)
  • Triggering command: /tmp/peasyai_venv/bin/pytest /tmp/peasyai_venv/bin/pytest tests/ --ignore=tests/pipeline --ignore=tests/rag -v -q -j DROP (dns block)
  • Triggering command: /tmp/peasyai_venv/bin/pytest /tmp/peasyai_venv/bin/pytest tests/ --ignore=tests/pipeline --ignore=tests/rag -q (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.