#10288 test: migrate example-library integration tests to pytest Pull request opened by LeonxLJX Replace the shell-driven validate.sh/commons.sh flow with a single parametrized pytest test that runs every example-library integration test in an isolated tmp_path, so pytest tears down generated files automatically. Fixtures express the shared steps from commons.sh: mdsh compilation, logging.yaml injection, and the ending-meltano.yml diff assertion. The test is skipped on platforms without bash/mdsh. Closes #6439 Description Checklist • I have read the contribution guide Was generative AI tooling used to co-author this PR? • Yes (please specify the tool below) Related Issues • Closes #XXXX Summary by Sourcery Migrate example-library integration testing to an isolated, parametrized pytest workflow while preserving existing validation and platform or infrastructure skips. New Features: • Add parametrized pytest coverage for all complete example-library integration tests, including per-test validation scripts and optional infrastructure-dependent cases. Bug Fixes: • Preserve validation of incomplete example-library directories by excluding them from test collection. Enhancements: • Replace the shell-driven example-library validation flow with isolated pytest execution and automatic temporary-file cleanup. Tests: • Add regression coverage for discovery behavior when required example-library fixtures are missing. meltano/meltano