full-system-verification

End-to-end system verification is automated by orchestrating unit, integration, and edge tests through a Python pytest-based runner. It auto-discovers test suites, executes targeted regression checks, and ensures system stability after code changes or refactors.

Regression checks in a CI pipeline are run using deterministic execution modes like quick, unit, integration, edge, full, or specific. The Python pytest-based runner supports flexible execution, timeouts, and targeted test selection to validate code changes efficiently.

Log streaming during automated test execution provides real-time output feedback while timestamped logs are saved to tests/temp/reports. This generates traceable and auditable records for validating system stability across development, CI stages, and post-deploy validations.

Pytest can be used to catch regressions during post-deploy validations by running comprehensive quality verification across unit, integration, and edge tests. The runner supports production validation scenarios with flexible execution modes and targeted test selection.

Quick mode should be used for automatic discovery and sanity checks, while full mode executes comprehensive regression across all test types. Deterministic modes allow fitting system testing to development, CI, and production validation scenarios based on required depth.

Python pytest is required to run this automated system verification. The centralized runner depends on a pytest-based framework to orchestrate unit, integration, and edge tests, execute targeted regression, and collect streaming feedback for stability checks.