E2E Tests to Pytest

[telemaco]

The intention of this issue it to move our end-to-end (e2e) tests to pytest, aligning them with our unit tests. tox is also included for isolated test environments, and tests are marked for easier execution.

Why?

• Framework Consistency: Using pytest for both unit and e2e tests reduces complexity and streamlines our testing process.

• Isolated Testing: tox ensures tests run in clean, consistent Python virtual environments.

• Flexible Execution: Pytest marks (e.g., @pytest.mark.e2e) allow for specific e2e test execution or exclusion. Also other features like pytest addoptions are used that allows to add parameters to pytest like: --no-container or --container-engine docker

• Other cool python+pytest features: Test parametrization, native json support...

Test migration status

• test/system/001-basic.bats
• test/system/002-bench.bats
• test/system/010-list.bats
• test/system/015-help.bats
• test/system/030-run.bats
• test/system/040-serve.bats
• test/system/050-pull.bats
• test/system/055-convert.bats
• test/system/060-info.bats
• test/system/070-rag.bats
• test/system/080-mlx.bats
• test/system/100-inspect.bats

[telemaco]

@rhatdan this issue is not finished yet. I'm going to reopen it. The intention of this issue is to track the e2e tests migration with the list that is above.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.