Split test doesn't need to be executed per Python version

[edenhaus]

Breaking change

Proposed change

Collecting will always report all tests, so no need to run it per Python version

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[emontnemery]

Nice!

[cdce8p]

Collecting will always report all tests, so no need to run it per Python version

Not always. I've added that explicitly in #126936 as we usually can't install all dependencies when adding a new Python version to CI. E.g. for 3.12 we added a conditional imports and modified the test collection

if sys.version_info >= (3, 12):
     collect_ignore_glob = ["test_*.py"]

Doing the collection with another version than the actual test run would thus fail.

At the moment, this doesn't seem to be necessary for 3.13 (#129442). However, I believe it's safer to keep the previous implementation and run it for each supported Python version.

[cdce8p]

Looks like it's safe after all. I just needed to disable an integraion in #129442: a0eaddc and it looks like the tests still pass.
AFAICT it's because the test collection is run for each pytest job again anyway. So collect_ignore_glob = ["test_*.py"] will just trigger later. Going to close #130192 then.