End nobo_hub config flow tests in CREATE_ENTRY or ABORT#170141
Merged
joostlek merged 6 commits intoMay 18, 2026
Conversation
Contributor
|
Hey there @echoromeo, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
21 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the nobo_hub config flow test suite to ensure flows always end in a terminal state (CREATE_ENTRY or ABORT), avoiding tests that leave flows mid-progress.
Changes:
- Extend several config flow tests that previously ended on an error form to retry with valid input and finish with
CREATE_ENTRY. - Split previously parameterized DHCP discovery scenarios into separate tests that each end in
ABORTor proceed to a completedCREATE_ENTRY.
Comments suppressed due to low confidence (2)
tests/components/nobo_hub/test_config_flow.py:235
- Remove the unused async_discover_hubs patch (or start the flow from the user step) since starting the flow with source="manual" calls async_step_manual directly and never performs hub discovery.
with patch(
"homeassistant.components.nobo_hub.config_flow.nobo.async_discover_hubs",
return_value=[],
):
result = await hass.config_entries.flow.async_init(
tests/components/nobo_hub/test_config_flow.py:277
- Remove the unused async_discover_hubs patch (or start the flow from the user step) since initializing the flow with source="manual" goes straight to async_step_manual and does not run discovery.
with patch(
"homeassistant.components.nobo_hub.config_flow.nobo.async_discover_hubs",
return_value=[("1.1.1.1", "123456789")],
):
result = await hass.config_entries.flow.async_init(
joostlek
requested changes
May 17, 2026
Member
joostlek
left a comment
There was a problem hiding this comment.
There's a merge conflict, can you take a look?
Contributor
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
…-test-terminals # Conflicts: # tests/components/nobo_hub/test_config_flow.py
joostlek
approved these changes
May 18, 2026
jnimmo
pushed a commit
to jnimmo/core
that referenced
this pull request
May 18, 2026
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
End
nobo_hubconfig flow tests inCREATE_ENTRYorABORTDiscovered during review of PR #168638
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: