run-all-tests

To run pytest test suites and generate a report, execute the test command in your repository root. This runs all tests and returns a concise results report with aggregated statistics and failure details for quick decision-making.

To include integration tests when running pytest automation, use the appropriate configuration flag to enable them. This ensures both unit and integration tests are covered in a single execution run without modifying local test artifacts.

Yes, you can run pytest tests without modifying local artifacts. This non-destructive test execution approach ensures your repository remains clean while still providing a complete results report with failure details and summary statistics.

The best way to check test suite health before CI/CD is running a comprehensive pytest execution that aggregates results. This provides clear failure details and summary statistics, helping teams quickly understand readiness for deployment.

Yes, this approach supports running both unit and integration tests in one batch. By applying configuration to enable integration tests alongside standard unit tests, it covers the full repository test suite in a single automated execution.

Standard pytest test runs may leave unwanted files if not configured for non-destructive execution. Using a non-destructive test execution approach ensures no local test artifacts are created or modified during the run.