Skip to content

Enforce async_load_fixture in async test functions #145709

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Jun 30, 2025
Merged

Conversation

epenet
Copy link
Contributor

@epenet epenet commented May 27, 2025

Proposed change

SSIA, as follow-up to #144534
If a function is async, and

  • it has a call to load_fixture, then the call should be migrated to async_load_fixture
  • it has a call to load_json_array_fixture, then the call should be migrated to async_load_json_array_fixture
  • it has a call to load_json_object_fixture, then the call should be migrated to async_load_json_object_fixture

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:
  • Link to developer documentation pull request:
  • Link to frontend 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:

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:

@home-assistant
Copy link

Hey there @ispysoftware, mind taking a look at this pull request as it has been labeled with an integration (agent_dvr) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of agent_dvr can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign agent_dvr Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@home-assistant
Copy link

Hey there @bieniu, mind taking a look at this pull request as it has been labeled with an integration (airly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of airly can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign airly Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@home-assistant
Copy link

Hey there @airgradienthq, @joostlek, mind taking a look at this pull request as it has been labeled with an integration (airgradient) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of airgradient can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign airgradient Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@epenet epenet force-pushed the epenet-20250527-1510 branch from acbc473 to a2ab53f Compare May 27, 2025 14:46
@epenet epenet marked this pull request as ready for review June 30, 2025 06:18
@Copilot Copilot AI review requested due to automatic review settings June 30, 2025 06:18
@epenet epenet requested a review from a team as a code owner June 30, 2025 06:18
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR enforces asynchronous fixture loading in async test functions by migrating existing calls and introducing a Pylint plugin to catch synchronous fixture usage.

  • Replace synchronous load_fixture calls with async_load_fixture and add await in async tests
  • Introduce hass_async_load_fixtures Pylint plugin to flag any remaining sync fixture loads
  • Update pyproject.toml to load the new plugin

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
tests/util/test_location.py Migrate load_fixture to async_load_fixture and add hass fixture parameter
pyproject.toml Add hass_async_load_fixtures to load-plugins
pylint/plugins/hass_async_load_fixtures.py New Pylint checker that enforces async fixture loading
Comments suppressed due to low confidence (3)

pylint/plugins/hass_async_load_fixtures.py:1

  • [nitpick] The module docstring is misleading. Update it to reflect that this plugin enforces asynchronous fixture loading in tests.
"""Plugin for logger invocations."""

tests/util/test_location.py:80

  • The test function uses HomeAssistant in its type hint but HomeAssistant is not imported. Add from homeassistant.core import HomeAssistant at the top of the file.
    hass: HomeAssistant,

pyproject.toml:164

  • The Pylint plugin module path should be fully qualified. Change this to "pylint.plugins.hass_async_load_fixtures" so that Pylint can locate the plugin.
  "hass_async_load_fixtures",

Copy link
Member

@edenhaus edenhaus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @epenet 👍

@edenhaus edenhaus merged commit e642cd4 into dev Jun 30, 2025
48 checks passed
@edenhaus edenhaus deleted the epenet-20250527-1510 branch June 30, 2025 09:56
@github-actions github-actions bot locked and limited conversation to collaborators Jul 1, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants