-
-
Notifications
You must be signed in to change notification settings - Fork 30
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
5 additions
and
318 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,59 +1,2 @@ | ||
# pylint: disable=protected-access,redefined-outer-name | ||
"""Test integration_blueprint setup process.""" | ||
|
||
import pytest | ||
from pytest_homeassistant_custom_component.common import MockConfigEntry | ||
|
||
from custom_components.integration_blueprint import ( | ||
BlueprintDataUpdateCoordinator, | ||
async_reload_entry, | ||
async_setup_entry, | ||
async_unload_entry, | ||
) | ||
from custom_components.integration_blueprint.const import DOMAIN | ||
from homeassistant.core import HomeAssistant | ||
from homeassistant.exceptions import ConfigEntryNotReady | ||
|
||
from .const import MOCK_CONFIG | ||
|
||
|
||
# We can pass fixtures as defined in conftest.py to tell pytest to use the fixture | ||
# for a given test. We can also leverage fixtures and mocks that are available in | ||
# Home Assistant using the pytest_homeassistant_custom_component plugin. | ||
# Assertions allow you to verify that the return value of whatever is on the left | ||
# side of the assertion matches with the right side. | ||
async def test_setup_unload_and_reload_entry(hass: HomeAssistant, bypass_get_data): | ||
"""Test entry setup and unload.""" | ||
# Create a mock entry so we don't have to go through config flow | ||
config_entry = MockConfigEntry(domain=DOMAIN, data=MOCK_CONFIG, entry_id="test") | ||
|
||
# Set up the entry and assert that the values set during setup are where we expect | ||
# them to be. Because we have patched the BlueprintDataUpdateCoordinator.async_get_data | ||
# call, no code from custom_components/integration_blueprint/api.py actually runs. | ||
assert await async_setup_entry(hass, config_entry) | ||
assert DOMAIN in hass.data and config_entry.entry_id in hass.data[DOMAIN] | ||
assert isinstance( | ||
hass.data[DOMAIN][config_entry.entry_id], BlueprintDataUpdateCoordinator | ||
) | ||
|
||
# Reload the entry and assert that the data from above is still there | ||
assert await async_reload_entry(hass, config_entry) is None | ||
assert DOMAIN in hass.data and config_entry.entry_id in hass.data[DOMAIN] | ||
assert isinstance( | ||
hass.data[DOMAIN][config_entry.entry_id], BlueprintDataUpdateCoordinator | ||
) | ||
|
||
# Unload the entry and verify that the data has been removed | ||
assert await async_unload_entry(hass, config_entry) | ||
assert config_entry.entry_id not in hass.data[DOMAIN] | ||
|
||
|
||
async def test_setup_entry_exception(hass: HomeAssistant, error_on_get_data): | ||
"""Test ConfigEntryNotReady when API raises an exception during entry setup.""" | ||
config_entry = MockConfigEntry(domain=DOMAIN, data=MOCK_CONFIG, entry_id="test") | ||
|
||
# In this case we are testing the condition where async_setup_entry raises | ||
# ConfigEntryNotReady using the `error_on_get_data` fixture which simulates | ||
# an error. | ||
with pytest.raises(ConfigEntryNotReady): | ||
assert await async_setup_entry(hass, config_entry) |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.