-
-
Notifications
You must be signed in to change notification settings - Fork 34.2k
Fixed issue when tests (should) fail in Smarla #146102
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
Fixed issue when tests (should) fail in Smarla #146102
Conversation
Hey there @explicatis, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
93e9bad
to
7d4d68a
Compare
7d4d68a
to
5b1dd0d
Compare
One check fails, because ConfigEntryAuthFailed is thrown in async_setup_entry but reauthentication flow is not implemented. This seems to be a new requirement and is something for a new PR or? |
*This occured after rebasing |
Instead you should raise |
* Fixed issue when tests (should) fail * Use usefixture decorator * Throw ConfigEntryError instead of AuthFailed
Proposed change
Fix issue when tests (should) fail, causing them to not fail or create lingering tasks.
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: